Rectangle 27 0

ASP.NET Development Server or Localhost IIS?


Another distinction I noticed is that Cassini runs as a 32-bit process and you have no control over it, whereas you can control the application pool of your IIS app to disallow 32-bit (assuming your IIS is running on a 64-bit server). This becomes especially important if your web application is going to call APIs in 64-bit processes such as SharePoint Foundation/Server 2010. When you debug your web app with Cassini as your debug server, you'll get "The Web application at url could not be found. Verify that you have typed the URL correctly" type errors when instantiating objects. If you debug using IIS with the app running in an app pool that runs as 64-bit with an identity that allows access to sharepoint database then you'll be able to debug properly.

Note
Rectangle 27 0

ASP.NET Development Server or Localhost IIS?


Agree re. port numbers. We currently generate an RSS feed for links to our dev websites, don't think I'll be able to make it work with Cassini

Also, if you need to test things like ISAPI plugins (a re-writer for example) I'm not sure how that's done on Cassini.

I know at one point I had an issue with Authentication not working as expected on Cassini (built in development server)

I use IIS all the time, it's pretty easy to setup, and you guys are already doing that...

On the "Web" tab of your web projects properties screen, you can specify a static port. For Web Site projects, this is in the standard property window.

The constantly changing port is also rather disconcerting to me. Also, for each web project in your solution it fires up another instance of a Casini server, and each one takes anywhere from 20 to 50 MB of memory.

Note
Rectangle 27 0

ASP.NET Development Server or Localhost IIS?


As I stated here: http://stackoverflow.com/questions/103785/what-are-the-disadvantages-of-using-cassini-instead-of-iis your developers need to be aware that Cassini runs as the local user, which is typically an admin account for developers. The development will be able to access any file or resource that their account can, which is quite different from what they will see on an IIS 6 server.

The other thing that's a pretty big gotcha is debugging web services is much easier using IIS and vdirs rather than separate Cassini instances.

Note
Rectangle 27 0

ASP.NET Development Server or Localhost IIS?


The main issue I've run into with the dev server is SerializationExceptions with custom security principals stored on the thread context. Details here.

Note