I have developed web application in .NET framework 3.5 in VS 2008, hosted in IIS under application pool ASP.NET 4.0 Integrated pipeline mode.
When I start debugging by hitting F5 button, it throws the error and debugger is not started.
But, If I open the same application in VS2010 and VS2013 and start debugging, the debugger started successfully.
If I browse the application's URL in the IE, it runs successfully. My problem is debugger not started in the VS2008.
What are the settings to be checked/changed to get working?
I have fixed by enabling the windows authentication for the respective website in IIS.
Refrrence:
1) http://blogs.iis.net/brian-murphy-booth/visual-studio-2008-unable-to-debug-asp-net-app-on-iis-7-0
2) http://forums.iis.net/t/1165570.aspx
Related
I have an asp.net core web api (asp.net core 2.2.6) published on a IIS local website. I have a few controllers that I'm trying to debug.
I saw on the website (docs.microsoft) that I should no longer attach the debugger to w3p.exe but to dotnet.exe instead.
The problem is that when I'm in Visual Studio (2017) I try to attach to a running process and the dotnet.exe is not visible, I cannot see it but it's correctly installed (ProgramFiles/dotnet/dotnet.exe) and I already uninstall/install .net core a few times and launch VS under admin mode but it did not work.
Does someone have an idea about this problem?
Thanks for reading,
Lio
I have an ASP.NET MVC 4.0 web project. I am caching state in the application cache using the Ninject InSingletonScope.
Every time I start Visual Studio 2012 debugging (F5), it kills my web app and my app cache also.
Note that I use IIS and not IIS Express, and I don't use Edit and Continue (see Visual studio debugger, dont stop website on stop debugging)
How can I prevent VS to stop my website every time ?
Instead of pressing F5, try going to the menu: Debug -> Attach To Process and attach to w3wp.exe for the website that is hosted on IIS.
for some time i've got a problem debugging my asp.net 3.5 Application with Visual Studio 2012. Each Time i want to observe which values are in an Collection,List or similar classes, Visual Studio hangs for some seconds and then for each Property of the Collection (like Count) there is no Value, but a message which says an timeout occured and i have to step further in the debugger, to activate it again. But when i step further (F10), Visual Studio hangs and i just can kill the w3wp.exe process and start debugging from beginning.
This Problem occurs only in my classic asp.net 3.5 application. Other Asp.net MVC or WinForms applications work just fine!
Anyone an idea?
I was also facing this issue and stumbled across this post:
Unable to start debugging on the web server. Could not start ASP.NET debugging VS 2010, II7, Win 7 x64
Dont know how but correcting the username/password of the app pool which was used by the ASP.NET application fixed the issue.
P.S: Application was working fine it not debugged with old app pool credentials.
Hope this helps!
Recently, I've installed VS 2010 on my machine. I also have VS 2008 installed.
Problem I'm facing is - I'm not able to debug the web services hosted on local IIS. Also, VS 2010 do not show message that source code is different.
To start debugging I'm attaching aspnet_wp.exe process. My breakpoint is in a method which is part of a Class Library project which is targeting to .NET v3.5.
Environment Details:
- Windows XP SP3
- VS 2005, 2008 & 2010
- IIS (v5.1) Targeting ASP.NET 2.0
- Web Service Targeting .NET Framework - v3.5
Does anybody have encountered same problem?
First there is an easiest method than attaching, to use the
System.Diagnostics.Debugger.Launch();
Next, go to the IIS and open the properties on you running web and check on "Web Site" tab if the the "HTTP Keep-Alives" is enable or not, and make it not enable.
If still not break, close the vs, and go to the project directory, and delete (first backup it) the xxxxx.suo file of the project. Then start it again and go for debug.
I am having issues debugging locally within Visual Studio 2010 on Server 2008 R2 (x64) for a new ASP.Net MVC application. I am able to debug using the VS Development Server (Cassini) but when I change to use the Local IIS Web Server and Create Virtual Directory, I am unable to debug. I get the standard VS message:
"Unable to start debugging on the web server. The web server is not configured correctly. ..."
Everything looks standard in IIS. The Default Web Site is running under the ASP.NET v4.0 application pool. The virtual directory that Visual Studio created is running under the same app pool. I am running Visual Studio as the Administrator account. It feels like some security setting or something is preventing this to work but I'm at a loss to what it could be.
The solution that worked for me was to run aspnet_regiis -i.