I have been trying to do development on Vista since I went full time Vista at home during the release candidates. Until recently it was nearly impossible to get any development done on this platform. Due to some hard working people at Microsoft, developing on Vista is now a pleasure. There are a couple of things you will need to do in addition to the normal Visual Studio 2005 install to be successful.
Install SP1 for Visual Studio 2005. This download is quite large and took me over an hour to install. Multi-tasking while installing this is not advised. Also, be sure to uninstall the Web Applications Project add-on, otherwise you will get a half hour into the installation only to have it error out.
Install the Visual Studio 2005 SP1 Update for Windows Vista Beta. This is the magic update that allows development on Vista to be a great experience. Before installing this update, whenever I would do ASP.NET development on Vista, the controls that I added to the aspx pages would not automatically be declared in the designer.aspx file. This made it so that I could not programmatically access any of the controls that I had declared in the aspx page. Installing this update fixed the issue and it has not happened since.
Setup Visual Studio 2005 to always run as administrator. Browse to your install dir (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE) and open the properties for devenv.exe. Switch to the compatibility tab and select "Run this program as an administrator".
Read this post and setup the Debugging Assistant if you are on a development machine. The post details some IIS configuration changes that need to be made as well as provides a link and instructions for setting up the debugging assistant.
Before installing the debugging assistant I would get the following error message when trying to debug from Visual Studio...
Unable to start debugging on the web server. An authentication error occurred while communicating with the web server. Please see Help for assistance.
Mike's article talks about how this is most commonly due to event handlers in global.asax like BeginRequest; however, I did not have any event handlers in global.asax and I was still getting the error. The most likely cause that I can think of is that I am using the ASP.NET AJAX Extensions (Atlas) RC1 and it is probably subscribing to pipeline notifications prior to AuthenticateRequest. Setting up Mike's Debugging Assistant fixed the issue that I was having and I am now successfully able to debug.
For some other interesting articles on working with ASP.NET and Vista/IIS7 check out this post from Rick Strahl and this post from Scott Guthrie.
Remember Me