At our shop, we develop on Windows Server 2008 VMS running IIS 7, like our production web server. With VS 2010 (and VS-2008, but much more 2010), I have problems with debugging my ASP.NET applications. If I throw an exception to the application, then I'll kill the debugger (Shift-F5) So that I can fix the wrong code. But after doing so, the process of IIS continues with the exception!
There may be many defective scenarios, sometimes exceptions go to the top in the IIS, and promptly ask me, "Do you want to debug this process [the choice of Visual Studio]" and the second time There is no sign, but the debugger goes into faulty process instead of starting. Next time I'm new to debugging.
What am I doing wrong here? Or is the wrong configured? I need a workflow that came back to me: run the web site, see exceptions, fix the code, run the web site again to verify the fix. Instead of manually working in the work manager to keep WP3 WP Will have to kill. Additional information: It may also be related to the fact that the solution includes both web site application and web service applications, the use of the site applicant is running in two virtual directories on both local IISs. Usually the attached debugger will either leave the web site or service, if there is a problem
I wonder Is there anything else that is hidden on being hidden? Can you set up Visual Studio to break all the exceptions? This exception dialog will open with the CTRL + ALT + E in the IDE Press.
By default, IDE will be broken only on user-unused exceptions. If a different exception is being thrown, then you do not know about it. Add checks to each checkbox in the "throw" column and try to run it through your code at another time. If another exception is arising, then Visual Studio will break on it.
Comments
Post a Comment