![]() ![]() The Debug configuration produces a slower, larger executable that allows for a richer interactive run-time debugging experience. There are two basic types of build configuration: Debug and Release. In Visual Studio, as with most IDEs, there are two phases to making code work: building the code to catch and resolve project and compiler errors, and running the code to find run-time and dynamic errors. Now, you want to make sure the code works properly. You've figured out the editor and created some code. This article describes how Visual Studio can help you find problems in your code by using build output, code analysis, debugging tools, and unit tests. Visual Studio includes a powerful integrated set of project build and debugging tools. When that URL is hit, IIS gives out a 401 just as when all handlers are enabled, so Visual Studio is happy again.Applies to: Visual Studio Visual Studio for Mac Visual Studio Code Therefore, we added the following line into our web.config handlers: I was not able to find out exactly which module it was, but I was able to find the class that is responsible:. But I've gone over the two sites side by side, and can't find any differences that account for this behavior.ĭoes anybody have a clue they can share with me? Or can anyone point me to any documentation on what exactly debugattach.aspx is/does, and what a DEBUG HTTP request does, and/or how VS uses them?įor performance reasons we removed all the handlers from the element of our MVC 5 project's web.config except for StaticFile and ExtensionlessUrlHandler-Integrated-4.0, and then started getting this error when debugging from Visual Studio.Īfter some investigation, we discovered that in normal use, whatever module that handles this request simply causes HTTP error 401 (unauthorized) to be returned. Looking at what's different between the old version that works and the new version that doesn't, the only things are the IIS setup of the virtual directories, and the web.config on the code itself. Nothing that seems to apply to this situation. I've googled debugattach.aspx, and the first several pages of articles that are returned all seem to refer to lockup's and timeouts, mostly on IIS 7 and VS 2005. ![]() My first thought was that VS must be writing out a "debugattach.aspx" file, and then invoking it, and maybe it doesn't have write permission to the directory, but, as far as I can tell, it does. ![]() If I run the same sequence on the old version, it shows the same thing, but first with a 401 code, and then the request repeated with a 200 code. I finally thought of looking in the Web logs, and found that whenever I hit the F5 key, the web log shows a DEBUG request for /debugattach.aspx, with a return code of 404 (not found). This occurs before it ever gets to "Application Start". The web server could not find the requested resource." I spent the better part of yesterday trying to figure out what resource it was looking for that it couldn't find. My problem is that, when I hit F5 in Visual Studio 2010 to begin debugging the new version, I get a "Unable to start debugging on the Web Server. The projects are set up to run in the IIS rather than VS's server. ![]() We've released our first production version, so I forked the code into a new directory tree, and set up new virtual directories in IIS to point to the new trees. I'm developing on an XP (SP3) machine with VS 2010 and IIS 5. ![]()
0 Comments
Leave a Reply. |