I have copied a project from one system to another with WinXp Professional Version2002 Service Pack 3. I have done everything right from formatting the system to re installation of OS, IIS, Sql Server 2005, VS2008, Application mapping for .aspx with C:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis .
ASP.Net Intallation from command prompt using aspnet_regiis -i, also the following
1. Open IIS manager.
2. Right click the website, and then select “Properties”.
3. In the “Web Site” tab, make sure the “IP Address” is “All Unassigned”.
Yet I have failed to debug.
My Visual Studio Info :
Microsoft Visual Studio2008
Version 9.0.30729.1 SP
Microsoft Visual Studio2008
Version 3.5 SP1
The web application targets .Net Framework3.5.
ie. The Project ->Properties
Target Framework : .Net Framework3.5
Thanks for the quick reply. However by then I had solved the problem and the solution is very silly.
I belived that if the project was working well on another machine with same h/w and s/w configuration then it should not have any major change in it. so I stick to my belief and I worked around it.
The Solution :)
What I did was recreated the virtual directory under IIS->default website with alias name and browsed to the folder that contained the web application. Then I closed the visual studio. I reloaded the project by clicking on the visual studio icon. Then I
removed the website project which was also the startup project in the solution explorer and re added the existing website project into the solution explorer and set it up as startup project.
Thats it . I saved all then build the individual projects individually. Finally I clicked the debug icon and ahaa it worked :) it did debug.
Sanjay1234
0 Points
2 Posts
unable to start debugging on the web server. The server committed a protocol violation. Section=R...
Dec 27, 2010 06:35 AM|LINK
I have copied a project from one system to another with WinXp Professional Version2002 Service Pack 3. I have done everything right from formatting the system to re installation of OS, IIS, Sql Server 2005, VS2008, Application mapping for .aspx with C:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis . ASP.Net Intallation from command prompt using aspnet_regiis -i, also the following
1. Open IIS manager.
2. Right click the website, and then select “Properties”.
3. In the “Web Site” tab, make sure the “IP Address” is “All Unassigned”.
Yet I have failed to debug.
My Visual Studio Info :
Microsoft Visual Studio2008
Version 9.0.30729.1 SP
Microsoft Visual Studio2008
Version 3.5 SP1
The web application targets .Net Framework3.5.
ie. The Project ->Properties
Target Framework : .Net Framework3.5
Its a Bread n Butter question.
Any suggestions will be appreciated.
Thanks in advance.
Rajneesh Ver...
All-Star
36815 Points
6757 Posts
Re: unable to start debugging on the web server. The server committed a protocol violation. Secti...
Dec 27, 2010 08:01 AM|LINK
See below link quite useful:
http://social.msdn.microsoft.com/forums/en-US/vststest/thread/2e3be101-b9c1-4b0d-a631-b840af1cdfc3/
www.rajneeshverma.com
Keep Forums Clean || Use Alert Moderators.
Sanjay1234
0 Points
2 Posts
Re: unable to start debugging on the web server. The server committed a protocol violation. Secti...
Dec 28, 2010 06:38 AM|LINK
Thanks for the quick reply. However by then I had solved the problem and the solution is very silly.
I belived that if the project was working well on another machine with same h/w and s/w configuration then it should not have any major change in it. so I stick to my belief and I worked around it.
The Solution :)
What I did was recreated the virtual directory under IIS->default website with alias name and browsed to the folder that contained the web application. Then I closed the visual studio. I reloaded the project by clicking on the visual studio icon. Then I removed the website project which was also the startup project in the solution explorer and re added the existing website project into the solution explorer and set it up as startup project.
Thats it . I saved all then build the individual projects individually. Finally I clicked the debug icon and ahaa it worked :) it did debug.
Cheers :)