It's a pain in the ass when have to open a Visual Studio project that is set to run on local IIS and Visual Studio
Visual Studio will always complain the lack of permission if the project is opened through double clicking the associated project file in Windows Explorer. The workaround to the problem is to change the windows registry so that every time a Visual Studio associated file is double clicked, it will open the Visual Studio in Administrator context, thus able to modify the IIS metabase. Below is a screen shot of an example which enable VS2010 and VS2012 to run in administrator mode.
Visual Studio will always complain the lack of permission if the project is opened through double clicking the associated project file in Windows Explorer. The workaround to the problem is to change the windows registry so that every time a Visual Studio associated file is double clicked, it will open the Visual Studio in Administrator context, thus able to modify the IIS metabase. Below is a screen shot of an example which enable VS2010 and VS2012 to run in administrator mode.
No comments:
Post a Comment