If you are debugging from a remote machine, you will need to run the Visual Studio Debugging Monitor on the remote machine, and open the firewall so that Visual Studio can connect to the debugger (msvsmon.exe does this for you by default). Other than that, it is the same as debugging it manually. The F5 debugging mode figures this out for you, and starts a convinient browser window for you to play around with the app. You can always manually attach the debugger via the Menu: Tools>Attach to Process … option, assuming you know what instance of W3WP.EXE worker process on your server the application is running in. Its designed to help you attach the debugger to the worker process running your ASP.NET application. I am going to try and provide you with step-by-step instructions below, and explain the several tradeoffs that you may need to make along the way.Ī little note about the purpose of Visual Studio's F5 debugging support: There are a handful of posts about trying to get this to work in various ways … most of which are missing key information needed to *really* get it to work. If not, please let me know.Ī number of people have been reporting problems when trying to debug their ASP.NET applications on Windows Vista with Visual Studio 2005 F5 debugging support. Thank you for your patience so far, and I hope that this resolves your problems. Also see the KB article 937523 (it is being published today, so may not be available yet). You can download the patch from connect here: Download. This patch also enables customers using Windows Vista Home Premium customers to use Visual Studio F5 debugging, who were not able to use this feature at all previously because Windows Authentication was not available on Windows Vista Home Premium. Please see Help for assistance" errors, that until now had to be worked around using the instructions below. Please see Help for assistance.", and "Debugging failed because integrated Windows authentication is not enabled. I've collected the various how-tos and gotchas about using Visual Studio 2005 and Visual Studio 2008 with IIS 7.0 applications into two detailed articles:īe sure to check them out for detailed info on working with both local and remote IIS 7.0 applications on Windows Vista SP1 and Windows Server 2008 RTM, doing local and remote debugging, and other stuff.Ī Visual Studio patch that fixes the Visual Studio F5 debugging of IIS7 applications on Windows Vista Home Premium and above has been released! This patch solves the "An authentication error occurred while communicating with the web server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |