I have both the .NET 1.1 and .NET 2.0 frameworks installed on my laptop because I frequently write software on both platforms. I recently had the need to create a new ASP.NET 2.0 website. I set everything up in IIS first (because I like to be able to dictate the name of the virtual directory and have it routed somewhere other than the InetPub\wwwroot folder for development.
Aside: VS2005 happily supports having a virtual directory pointed at a folder with a name other than the virtual directory name :) VS2003 and prior didn't support this, so I didn't have nearly as many hoops to jump through when setting it up. For instance, my virtual directory might be named TestSite and point to a folder named Source within the TestSite folder. (I might have other peer folders, such as DbScripts, Documentation, etc all within the TestSite parent folder. I no longer have to jump through hoops to make that work. :)
Anyway, I set it up and began writing some framework code for the site, setting up some master pages, themes, et al. When I went to browse to the page I was greeted with a 'Mutex could not be created' error page. Not deterred (and, frankly, half expecting the exception in the first place), all I had to do was this:
- Grant myself (rather the user the site impersonates) Full Control to the %WINDIR%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files folder.
- Then, as I have the tradition of doing, delete the 'TestSite' folder (and all others for that matter) from the 'Temporary ASP.NET Files' folder.
- Perform an IISRESET.
Once those steps were done, the site worked like a charm! Happy Coding.