Beware the perils of the VS2005 Development Web Server
One of the slick new features of Visual Studio 2005 is the ASP.NET Development Web Server - basically a scaled down web server that you can use during web application development instead of using IIS. I've been using it for a while, and it generally worked great. However, I recently tried to deploy my web app to an IIS server, and it suddenly stopped working. It turns out that the behavior of one the 3rd party ASP.NET server controls I was using changed when I switched to IIS. In this case, it was a chart control that suddenly stopped rendering its images correctly.
I haven't yet figured out the fundamental problem (the control wasn't designed for .NET 2.0, so it could be a version issue). I'm not bashing the Development Web Server - it's a very handy feature. The moral of the story is that the DWS is not IIS - don't be lulled into believe that they are interchangeable.