<p>Currently our dev team set up all the websites they're working on in IIS on their local machine. We're thinking of switching to using the built in ASP.NET development server instead.</p>

<p>Is this a good idea? What are the pros / cons of using the ASP.NET dev Server? Are there any gotchas we should be aware of?</p>

<p>Thanks.</p>

<p>NB: Running on Win XP / IIS 5 / VS2005</p>

<p><strong>Edit:</strong></p>

<p>Didn't realise it was called Cassini.. More answers for <a href="https://stackoverflow.com/questions/103785/what-are-the-disadvantages-of-using-cassini-instead-of-iis">Cassini v IIS here</a>.</p>

There is nothing that the ASP.NET Dev WebService can do that IIS can't (You can set breakpoints etc, just attach the VS debugger to the ASP.NET runtime).
However, the ASP.NET Dev WebService does not represent a true production environment, and as such you can get caught by gotchas that you wouldn't expect when you deploy to production.
Because of that, I mandate that all development is done using IIS on a local machine. It doesn't take much work to configure a site in IIS.