We help IT Professionals succeed at work.

Visual Studio 2008 view in browser localhost points to wrong port

GliderGuy
GliderGuy used Ask the Experts™
on
When I click the "View in Browser" button to view my page, the localhost launches with a port number that is always just 2 digits off from the correct value. Editing the URL makes it work. Browsing to the page via the local server on the task bar also works. Hosts file and .NET configuration are all normal. It appears to be a Visual Studio configuration issue, but I can't get it to work. Ideas?    
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2013

Commented:
not sure if i got the exact problem you are facing....but you might want to check your website settings..
Right Click your Website in Solution Explorer -> Startup Options->Check the Server Settings there.

Author

Commented:
Thanks for answering on a holiday weekend! Start Options are all defaults including "use default web server". Here's a little more info. I'm writing pages for an ASP.NET application. I make changes to a page and wish to test it. With the page openin VS I click the "View in Browser" icon and IE launches with the URL: http//:localhost:1234/... and generates an "I cannot display the web page" error. If I hold the mouse over the  web server icon on the taskbar I get a tooltip identifying the port as 1236.  Change the port number in the IE URL and the page opens. The weird thing is the port number is always exactly two digits lower than the correct port. Not a show stopper, but really annoying.
??????
Top Expert 2015

Commented:
Not a solution, just something to test. Is it IE8? Does the problem go away when you change to FireFox as your default browser in Visual Studio?
Top Expert 2013

Commented:
Top Expert 2013
Commented:
bit more detailed steps: http://forums.asp.net/t/1235447.aspx?PageIndex=1
in case if it is the anti-virus issue...

Author

Commented:
Changing the settings in Eset NOD 32 AV solved the problem! I like the Eset product and have had few problems with it. Maybe that's why I didn't think of it.
Thanks!