Web site on IIS vs. Web site on File System

Mikhail Arkhipov posted earlier about How to move file system Web site to IIS in VS 2005 describing the reasons you want to move and steps to move to IIS.

My 2 cents on this. The main reason one would do this (and it is not mentioned) is when (because) she wants to follow security best practices - for example I (and the team of developers) work with windows user in Active Directory with low permissions. I add this user to the local IIS_WPG group - this way we grant this user permissions to execute stored procedures within the database on the database server on the network.

It looks like you can move easily but imagine that you have to move when the whole solution is in Source Safe and there are other developers that work on it. It turns to be a pain in the ass. I don't think that the whole thing is a bug, but this makes web site on file system totally useless.

Related Posts:

• Web Application Projects Model - Source Safe Integration
• VS 2005: Web Application Projects Beta V2 is available
• VS 2005: Web Application Project is more Source Safe Friendly
• Visual Studio Web Application Project Preview and Deployment Issues
• VS 2005: Web Application Projects for ASP.NET is available
• VS 2005: New (VS 2003 like) Project Option for ASP.NET
• VS 2005: HTML validation checking
• Visual Studio 2005: Web Deployment Projects Add-On
• Convert Web Application from VS 2003 to VS 2005
• Exclude From Project Issue Fixed in VS 2005 RTM