Dave Mellors - All Comments

re: Visual Studio development web server dynamic port numbering problem

Nikola — Thu, 08 May 2008 18:04:57 GMT

I really think that is more VS2008 (the one that I'm using) and NOD issue,but I am not sure. I will continue with this matter and if I come up with something I will inform you!

Thanks anyway

re: Visual Studio development web server dynamic port numbering problem

Dave Mellors — Thu, 08 May 2008 06:57:25 GMT

The problem I describe is where the ASP.NET development server reports that it starts on port x but when the browser window is started by Visual Studio it tries port y. If you are getting an XML Parsing Error then it sounds like something is responding to your request although I guess it might be something else other than the web server.

Have you tried creating a new ASP.NET web site using Visual Studio and seeing if you still get the problem - this would then help to identify if the problem is with your project or not.

Also, you can see what port your web server is using or what is using the port you think your web server should be on by running a netstat -ab from a command prompt and looking for the port number or [WebDev.WebServer.EXE].

Let me know how you get on.

re: Visual Studio development web server dynamic port numbering problem

Nikola — Thu, 08 May 2008 00:11:55 GMT

Hi Dave, unfortunately this solution did not worked for me. At the beginning I was getting messages like:

-----------------------------------------------------------------------

XML Parsing Error: no element found

Location: http://localhost:xxxx/xxxxxxxxxxxx/xxxxxxxxx

Line Number 1, Column 1:

-----------------------------------------------------------------------

But then I realized that my problem was not in the XML but it was port number mismatch. So the above solution as i mentioned didn't worked, do you have any other (anybody)?

Thanx

re: Visual Studio development web server dynamic port numbering problem

Dave Mellors — Mon, 28 Apr 2008 22:11:53 GMT

Thanks Eric. Sorry to hear this didn't fix your problem and that the support hasn't worked for you.

You have probably already spent some time trying to sort the problem and I can't say I could do any better but a fresh pair of eyes sometimes help. If you fancy another go at troubleshooting the problem I'd be happy to try and help (drop me a message with your email address using the contact link on my blog)

re: Visual Studio development web server dynamic port numbering problem

Eric — Mon, 28 Apr 2008 21:38:19 GMT

Hi Dave,

I talked to Eset, but they said that this was the solution. But still it didn't worked for me. I asked myself how many people first talked to Microsoft and how does Microsoft finds it that there development tool is standard blocked by nod32?

re: Visual Studio development web server dynamic port numbering problem

Dave Mellors — Mon, 28 Apr 2008 10:22:07 GMT

Eric, thanks for the comment.

I think it's good that a virus scanner has this sort of feature but I guess there is an issue in that I think most of us probably didn't know the feature existed until we came across this problem. Although, it sounds like your problem may be unrelated.

I think my main problem with Norton/Symantec (and McAfee) was the support wasn't very good and they rarely seemed to develop the product to address the problems that users experienced. My impression of ESET is quite different so I'm surprised if the ESET technical support team weren't able to help you - I'd certainly be interested to hear what they had to say and as I get a lot of visitors who use their software I am sure they would be interested in your experience of the support.

re: Visual Studio development web server dynamic port numbering problem

Eric — Mon, 28 Apr 2008 07:18:48 GMT

It didn't work for me. In the active mode list the VS server wasn't mentioned. I did the other suggestions which didn't work either. Even disabling Web Access or nod32 completely. So I removed nod32 which did the job for me. I find it bad that a "Virus scanner" does this. Is nod32 becoming the new New Norton?

re: Visual Studio development web server dynamic port numbering problem

Christian Moller — Fri, 25 Apr 2008 19:49:50 GMT

Thank you very much Dave it did the trick!!

re: Visual Studio development web server dynamic port numbering problem

jimbob — Wed, 23 Apr 2008 13:04:11 GMT

worked for me too, thanks (was doing my head in)

re: Visual Studio development web server dynamic port numbering problem

murdoc — Mon, 21 Apr 2008 19:58:57 GMT

Thank you very much Dave!

re: Visual Studio development web server dynamic port numbering problem

Gavin Hewins — Wed, 09 Apr 2008 14:49:39 GMT

Many thanks for that. This problem only occurred for the first time for me today (after an ESET update).

I was getting very frustrated by this until I came across your solution.

Regards

Gavin

re: Visual Studio development web server dynamic port numbering problem

Elrond — Fri, 28 Mar 2008 07:35:52 GMT

Thanx Stavros! Your solution worked for me.

re: Visual Studio development web server dynamic port numbering problem

Miroslav Majtaz (ESET Tech Support) — Wed, 26 Mar 2008 16:46:46 GMT

Thanks. We'll add that to our KB.

re: Visual Studio development web server dynamic port numbering problem

Dave Mellors — Wed, 26 Mar 2008 08:41:55 GMT

Thanks for the feedback from everyone. I've contacted Eset technical support suggesting they might want to put it on their support section.

re: Visual Studio development web server dynamic port numbering problem

Luis Santamaria — Thu, 20 Mar 2008 08:20:57 GMT

Hello Dave!

Thanks a lot for this “tip”. I had the same problem for, like one week, and nobody knew or could say what the problem was. It was until now when I read your article that I realize about the problem’s reason.

Thank you again!

-Luis