Dear everybody,

I've just installed Microsoft Visual Studio 2008 on Windows Vista Ultimate. I created "New Web Site" and Started Debugging the page to see the blank page rendered. To my surprise, IE 7.0 displayed an error message saying: "Internet Explorer cannot display the webpage". I spent some time investigating and here is the result:

• The page going to be rendered assumes port 49791: http://localhost:49791/WebSite3/Default.aspx
• The ASP.NET Development Server operates under different port no: 49793
• After changing the url above manually to use the port of ASP.NET Development Server, the webpage gets renderred correctly: http://localhost:49793/WebSite3/Default.aspx
• ASP.NET Development Server uses dynamic ports. I noticed that Debugging process always assumes port number lower by 2 than the real port number of the ASP.NET DevSer. Therefore Debug process never runs and displays the page.

I do not want to manually edit the local host URL after every page rebuild, so my question is following:

• How to make the "Start Debugging" function to use appropriate port of the ASP.NET Development server? How to make Visual Studio to open the page being debugged?

To mention couple of things I tried: I reinstalled Visual Studio2008, tried to disabled IPv6 as some threads recommend - nothing helps.

Any idea would be welcome, because I have no idea what else to try. Thank you in advance.

Does anybody have commnents or ideas what could help? I will gladly try anying expect formatting my hard drive. :-)

What antivirus are you using? does it mess with your ports? How about firewalls? do you have them set too hight?

I'm on Vista Ultimate also, I have no problem with VS2008. I have CA Antivirus and using the windows firewall. You might want to try and disable your security temporarily and see if it works. You should not have to edit URL's to get it to work. It should work once you hit the debug button and run the web app.

Hello NesNYC718. Thank you a lot for replying.

I use NOD Antivirus. I tried to disable theantivirus, disabled firewall, but still after pressing the F5 key for Debugging, the IE7/Internal Web Browser/FireFox opened but they still refered to different port number - and the page did not run.(I had to manually change the port number)

Yes, you are correct, maybe, I should try to uninstall the antivirus and maybe to use something different.

NesNYC718, I noticed that if I create a new C# Proejct (ASP.NET WebSite), I can get page open appropriatelly. This happens only, when I create New WebSite - hopefully to understand the difference. There must be a solution to this.

• Should the port in the URL of the debugged page be the same as the port of ASP.NET Development Server, please?

Hello everybody,

• Could any body confirm please, if the port of the ASP.NET Development Server should be the same as the port of the debugged page (ex: http://localhost:49791/WebSite3/Default.aspx), during debug process?

Thanks,

Rene

Bunkai:

I use NOD Antivirus.

Is that Norton? If so, I'd cosider an alternative. Something is not letting you apps talk to eachother and the security software is most likely to blame. See if you can set your security software to make exception for the processes in question. I recall a while back that some Norton products have a "saftey" feature that disallows apps from talking to themselves. You can probably find such settings in the advanced features but I'd get rid of it all together. Uinstall it and see if that does the trick.

Bunkai:

Could any body confirm please, if the port of the ASP.NET Development Server should be the same as the port of the debugged page (ex: http://localhost:49791/WebSite3/Default.aspx), during debug process?

Where are you "publishing" this page to? Did you create a new website on you local file system or a remote website? The development server's operation is seamless and you should not have to worry about what port it's using. Everything is automatic as IE is launched with that local address but debugging should be enabled in IE as well, did you check your "Internet Options" and see if you have debugging enabled in IE?

Hello NesNYC718,

 Thank you for paying attention to my problem. Right now I am experimenting and trying to find an answer to my problem.

However, to answer your questions:

•  NOD Antivirus that I use is product by ESET (http://www.eset.com/). During one of my experiments I disabled Windows Firewall, which I use the same as you, the NOD Antivirus, and the Widnows Defender. I disabled them all in once, and even stopped them as services. The problem persists: the ASP.NET development server uses a dynamically created port (ex: 53013), however the webpage that gets opened always refers to a port lower by two(ex: http://localhost:53011/WebSite3/Default.aspx)

• I am publishing this page in my local system - therefore I rely on ASP.NET Development Server, so I do not have to install IIS.

I noticed, that the IE7 refers to Internet with the wrong port, which is lovered by two. However, when I correct the URL by typing correct port number, the IE7 starts referring to Intranet. If I preset detault web browser to FireFox for example, the same things happens - the wrong URL is present. When I create "New Project" - the problem diminishes, and everything works fine. When i create "New WebSite" the problem always persists.

• I will keep reading and will inform you if there is anything new. If anybody has a new idea I woud be happy to know about it.

Thank you,

Rene

For everybody having this problem, I have found a solution:

• This problem occurs, when NOD 32 Antivirus by ESET is installed, version 3.0.621.0
• The Antivirus Software contains Web Access Protection that automatically disables the dynamic port of ASP.NET Development Server.

The Solution:

1. In the Advanced setup of ESET NOD Antivirus you need to locate the section shown in the image below and uncheck the web development server.
   
2. Make sure you stop the web development server if it's still running and then try debugging from Visual Studio again.

---------

Or, follow these steps that basically describe the same solution in step-by-step way:

1. DoubleClick on Nod32 icon on tray and Open it up.
2. if it is not in "Advanced Mode" , switch to Advanced Mode. ( you can do it by clicking on the bottom-left link "Display:Standard Mode" and then click on "Toggle Advanced Mode" )
3. then goto SETUP section. then on the Right Pane click on "Antivirus and Antispyware protection". the panel should be opened.
4. now in the "Web Access protection" click on "Configure..."
5. from the left Tree go to path : "Web access protection > HTTP > Web Browsers"
6. now you should see visual studio 8 "devenv.exe" in the list .
7. click on it twice till you see a cross sign in the box. ( Note on CROSS sign , not mark sign ! )
8. with this cross sign you tell the Nod32 that this program should not be scanned and filtered for web access.

I hope that this helps. I want to thank to NesNYC718 for his attention and attempts to help me.

Bunkai:

The Antivirus Software contains Web Access Protection that automatically disables the dynamic port of ASP.NET Development Server.

Yep, just what I thought. "Security" software is designed for folks that haven't a clue about really protecting their machine and there for use "overkill" features to insure "safety," LOL! Even then, I've seen people get attacked anway.

Bunkai:

I hope that this helps. I want to thank to NesNYC718 for his attention and attempts to help me.

You're welcomed.

I Had the same problem running on Vista.

My solution was removing the next line in the windows host file C:\Windows\System32\drivers\etc\hosts

::1  localhost

This is an IpV6 entry. Put a # in front of it.

Thanks! My solution was the same, although I'm also with Eset Smart Security

zorry:

Thanks! My solution was the same, although I'm also with Eset Smart Security

LOL! It's not so "smart" if it's you have to tinker with it to make you're apps work. LOL!

Arien:

I Had the same problem running on Vista.

My solution was removing the next line in the windows host file C:\Windows\System32\drivers\etc\hosts

::1  localhost

This is an IpV6 entry. Put a # in front of it.

 

Hi!

Thank you so much! You save my life, in the past 4 days I start to be in madness with this issue. I wanted to work and I couldn’t!  Thanks a lot!!!

Thanks a lot.

I'm also using Nod32 by ESET.

unchecking ie solved my problem