Disabling Visual Studio Development Server - Any way to do this per project?

views:

answers:

+3 Q:

Disabling Visual Studio Development Server - Any way to do this per project?

When debugging my website project I usually go to start options in the web project's properties and select 'Don't open a page' and 'Use custom server' with a url that's in my host file pointing to my local IIS.

Even when I do this though visual studio still spawns it's own Development Server instance every time I hit f5.

Is there any way to disable this?

Also for web application projects that have shared ascx files for instance Visual Studio will also launch an instance of Development Server each time I debug the solutions for each for these projects. This results in a million instances of Development Server running on my machine at any given moment.

Is there any way to disable development server for a given project completely? Without pointing it to a localhost sub application?

Click on Project, Properties, Web. Under Servers,select Use Local IIS Web Server. If the site has not been created on IIS yet, click on Create Virual Directory. Your project will now run in IIS when you debug.

Johnny DropTables 2010-08-13 07:36:02

Any way to do this on a website project? I think this only refers to web application project types.

BrooklynDev 2010-08-14 06:55:55

When I create a website project, I prefer to host the site on IIS, mostly because it is easier to run the IIS application pools under a service account, is more flexible with authentication options, and is more like production (when compared to Cassini).

Unlike the Web Application Project, a website gives no built-in support for "adding itself" to your local IIS. If you already have a filesystem-based website project, what I usually do is:

Remove the website project from my solution.
Configure the application/virtual folder in IIS to use the filesystem-based website I just removed.
Right click on my solution and select Add Existing Web Site.
Choose "Local IIS", instead of "File System", and pick my site from the list of applications.

Besides the fact that it is manual, it makes for smooth debugging without the development server, and TFS is sufficiently aware of the file system that it manages my source code correctly

I hope this helps.

kbrimington 2010-08-17 01:52:54

Yea I suppose this may be the only solution to having a million cassini instances all the time.The reason I'd prefer not to use localhost for my web projects is two fold:1. The web project that interface with the user directly is almost always expecting to live in root. 2. The project's that aren't directly navigated to with a browser don't need to be run independently.Since all my projects are in team foundation server and I'd like any new user to be able to pull a project down and run it cassini seems to be the most flexible of the host config choices.

BrooklynDev 2010-08-17 15:57:12

Requiring a localhost/appname creation is relatively invasive to require for any developer touching the system. Plus that config precludes the application from running in root. Requiring every user to create a new IIS site for the app isn't super easy either. What I want is for any developer to be able to take the project down from source control and run it. Cassini seems to be able to serve this purpose for the most part. I just wish I couldn't turn it off entirely for some projects or disable it for when I choose 'use custom server', cassini always seem to want to spawn a server instance.

BrooklynDev 2010-08-17 16:04:10

ansaurus

tags:

views:

answers:

Disabling Visual Studio Development Server - Any way to do this per project?

related questions