Accessing the ASP.NET Web Configuration Tool in Visual Studio 2013

Accessing the ASP.NET Web Configuration Tool in Visual Studio 2013

Rate This
  • Comments 25

As many of you have noticed, the option to select “ASP.Net Web Configuration Manager” is no longer in Visual Studio 2013 Preview. This is due to the removal of the Visual Studio Development Server (or Cassini) from the product. However, we understand that many people have gotten used to using the Tool, and so here are the steps by which you can still run the manager. Note that these instructions only work for sites running on the .NET Framework 4.0 and above.

  1. Open the Command Prompt (not as administrator)
  2. Navigate to the folder where IIS Express is installed on your machine.
  3. In the command line spin up a IISExpress site with the following prompt: “iisexpress.exe /path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ASP.NETWebAdminFiles /vpath:”/ASP.NETWebAdminFiles” /port:[port] /clr: 4.0 /ntlm” using the following values for the [param]:
    1. [port] – any port you have free in IISExpress (I use 8082 in the example below)
  4. This should launch an IISExpress instance of the Configuration Manager Site<br/>clip_image002
  5. Open your browser
  6. In the URL enter the following “http://localhost:8082/asp.netwebadminfiles/default.aspx?applicationPhysicalPath=[appPath]&applicationUrl=/” substituting the [appPath] with the absolute path to the Visual Studio Project folder with the solution file in it.

Congratulations, you now have your ASP.net Web Site Adminstration Tool running as before.

  • Why why why why why???!!!!!   Why make it so difficult?!  This was SO helpful for creating users and roles.

    Sigh,

  • I really don't have time to make an extension to VS to add this back in. Everyone's using it so why can't you make our lives easier and keep it there?

  • OH MY GOD. The Visual Studio team are a bunch of morons. Put this feature back! This f'ing command line bs doesn't work. The tool was so fast and convenient..

  • For anyone having issues with the invalid folder path, on my case it is simply because by some reason it is using a shortened version of my user name instead of my full user name when copying the config file. The worst bit is that when it tries to access it it searches on whatever profile folder associated with my current user.

    ie:

    My current user: Comp-Name\MyName

    My user's folder: MyName.Comp-Name

    The folder iisexpress tries to copy the config file to: Comp~1~MyN\AppData\Local\Temp...

    It then tries to get the config file from the folder associated with my profile: MyName.Comp-Name\AppData\Local...

    This is also why it doesn't work if you are running the cmd prompt as Administrator.

  • Why Microsoft ???? Why ???? ... I understand ... It was too easy in Vs 2012 ... Do you want to stop for a moment and let us breathe? I'll be back in Vs 2012. O God, forgive them 'cause they know not what they do ...

  • Guys, I've found a work-arround. You need to install VS2010 in the same machine. Then open the project in VS2010 and run the tool. Configure the users and roles. Close and open the project with VS2013.

    At least we can use the tool this way.

  • That change pretty much screws any sort of development in corporate shops since IIS express is worthless if you are using modules and lots of big shops don’t allow IIS on desktops. Thanks MS for screwing us again.

  • when i do all of these solutions,they do not also work... i do not why microsoft did not add asp.net configuration in visual studio 2013

  • I also have an "Invalid application path"

    I used: iisexpress.exe /path:C:\Windows\Microsoft.NET\Framework\v4.0.30319\ASP.NETWebAdminFiles /vpath:”/ASP.NETWebAdminFiles” /port:12345 /clr:4.0 /ntlm

    if worked when I removed the spaces and renamed the vpath:

    iisexpress.exe /path:C:\Windows\Microsoft.NET\Framework\v4.0.30319\ASP.NETWebAdminFiles /vpath:”/WebAdmin” /port:12345 /clr:4.0 /ntlm

    Thanks for this great blog post! I was really missing that option in Visual Studio!

    Best regards,

    JP

  • Works fine.  While I am a little displeased that the functionality has been removed and a more suitable error provided besides the error I am receiving:

    "Error invoking 'Ad&ministrator Website'. Details: Exception has been thrown by the target of an invocation." ,

    an alternative should have been made to administer the Membership database. If IIS Express can run the admin site, then the UI should have been updated to spin up within the app domain the admin site.

    Thanks for your workaround. I really didn't want to have to keep VS2012 around just to perform this task.

Page 2 of 2 (25 items) 12