Chris Szurgot posted
complaints about the changes to web projects in VS2005 - especially the elimination of the project file for web projects. I quite agree with him (I've been meaning to blog about it for some time). Now, VS2003 had it's problems - the evil .webinfo file in particular. Being able to open a web project directly, without setting up a virtual dir, is brilliant. But the complete elimination of the project file is not, in my opinion, a good change.
I don't really understand the problem that they were trying to address by eliminating the project file, but it seems to do more harm than good. I've actually lost capabilities, such as the ability to selectively exclude files from a project. Also, I was hoping that the next version would supporting file links - a feature in VS2003 for non-web projects - but obviously that's impossible with the new model.
My biggest complaint, though, is that the web project model is simply very different from non-web projects. I would guess that many, if not most, web site developers will eventually create class libraries, which means that most developers will be forced to use two different development models. Why?