I have this love-hate relationship with Visual Studio 2005 Web Dev. One of
the things I couldn't stand in Visual Studio 2003 was how when different people
would check out the Web project file and then check it back in, assembly
references would be messed up. Usually the assembly location would change, or
someone would reference either a project or DLL and you'd have this
mix-and-match nightmare to fix every time you did a Get Latest Version from VSS.
OK, that really wasn't too bad. What was really bad was dealing with people
checking in pages that wouldn't compile! At least now in Visual Studio 2005, you
can delete the offending page locally, or simply work around it (since ASP.NET
2.0 compilation is radically different). What I really hate in VS2005 is
when you delete or move files, someone else still has the old files and then
checks in the old file that you deleted because Visual Studio will happily add
the deleted file as a "new file" from your co-workers machine. So to use the new
model, you have to be diligent about getting latest version from VSS before
checking in your work and making sure you check only the files that you really
mean to check it. It is quite easy to simply right-click on the solution or
project file and just check in everything and hose up everyone else. Of course,
you could go back to using a project file now thanks to
ScottGu...but then you'd be stuck with having to have a project file.
:-)