One of the most concerned thing for developers before upgrading to Vista RTM is probably the uncertainty of development features in Vista RTM. Some of mostly asked questions, does the IIS still work the same way it used to be? Is Visual Studio 2005 fully compatible and running as expected? Can I still work with “http projects” in Visual Studio 2005?
Earlier this week, I had chance to get the Vista RTM bits and finally decided to upgrade my existing Windows XP to Vista (of course after full backup in case unexpected thing happened :). Everything worked well including most existing applications, except one thing: ASP.NET doesn’t work at all.
This is quite surprising. If you installed Vista from scratch (clean install), you may have visit Scott Guthrie’s post and grab some tips to enable ASP.NET (IIS7) in Vista.
If you are upgrading from Windows XP to Vista like in my case, unfortunately you will find out that Scott’s technique didn’t work. The first step will fail — no matter how many times you tried. The “Enable ASP.NET” in Window Features will generate an error in the end of configuration like “An error has occured. Not all of the features were successfully changed”.
When you get that error message, the nightmare came. Vista RTM is just get out of the door last week, and there is no support or KB yet in this area.
In this post, I will share how I overcome this problem by manually performing extra steps to make ASP.NET works in Visual Studio 2005. Before I start, you should understand that Vista RTM installation comes with total security. That means all web development features are locked down.
The following steps will unlock the web development features so you can get back to your web development:
- Open “Services”. Now you can do this very easy by typing Services in the search textbox located at the bottom of start menu panel.
- Find “Windows Process Activation Service”. Change its Startup Type to Automatic, and “Start” the service.
- Next, find “World Wide Publishing Service”. Notice that you can not directly start this service because it is in “disabled” state. The trick is by changing the Startup Type to Automatic first, then you can start this service.
- Next, open “Command Prompt”. Again you can do this quickly by typing “cmd” in the search textbox.
- Run this command “aspnet_regiis -i” inside ASP.NET 2.0 Framework folder. This will re-register ASP.NET 2.0 handlers and mapping to all existing web applications.
- Finally, run this command “net start w3svc”. Your web server should be started perfectly at this time.
- Try to open one of your HTTP project in Visual Studio 2005 and run one of your webform. Here you go.
Good luck and enjoy the best operating system ever.