Development in IIS or on file system

ASP.NET 2.0 installs web projects by default in the file system, leveraging
the increased security of the new personal web server, rather than relying
on hacker prone IIS. However, it strikes me that this will add more
headaches for testing because your development doesn't use IIS. For
example, you lack the benefits of testing withing the VS IDE with debugging,
as well as identifying IIS issues upfront. We work in an environment where
Microsoft's updates are automatically downloaded and installed, keeping IIS
ideally as up to date as Microsoft is able to make it.

Aside from the obvious security benefit of not using IIS, are there other
advantages/disadvantages/work arounds that should be considered here?

Thanks in advance.

Mark



.

Relevant Pages

  • Re: Development in IIS or on file system
    ... >ASP.NET 2.0 installs web projects by default in the file system, ... >the increased security of the new personal web server, ... >headaches for testing because your development doesn't use IIS. ... >Aside from the obvious security benefit of not using IIS, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Development in IIS or on file system
    ... I can copy the files from the file system to my local IIS to test ... >>the increased security of the new personal web server, ... >>Aside from the obvious security benefit of not using IIS, ...
    (microsoft.public.dotnet.framework.aspnet)
  • File System web projects - ASP.NET 2.0
    ... ASP.NET 2.0 installs web projects by default in the file system, ... the increased security of the new personal web server, ... more headaches for testing to stop using IIS for development. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading