Hi "admin" ( :p)
I have to say i did not have alot of time when i had to choose whether or not to convert our current project to the new Web Application format. So i did not read all the documentation there is. I did it based on the problems i had. For instance the 'default' webprojects had several disadvantages that encouraged us to upgrade:
- SLOW - we use integration with CVSNT using a custom connector called "PushOk" that allows visual studio integration just like with VSS on both LAN and WAN. the moment we dropped a webproject in our solution of around 20 projects, it took ages to finish updates and checkins and refreshes. (main reason)
- What's in is in - meaning that every file in the folder is automatically a sourcecontrolled item. things such as logfiles and other runtime created files are considered by the web project to be under sourcecontrol. There was no default behaviour like in the normal projects.
- NO project file (another main issue) - All information is stored in the solution file. It drove us crazy that when adding a file, opening a webpage, or even recompiling it wanted to check out the solution again. (seemed totally random at some point..) (and then you couldn`t because someone else had the solution checked out because of the same issue)
- No default namespaces, just one big pile of webpages/classes - We like to work as neatly as possible. that includes adding everything nicely into namespaces etc. the default webprojects seems much more geared to the so called 'quick and dirty' approach.
As i said i did not have all the time in the world to find fixes for some of the problems i have described. But nor did i have to, since migrating to the new WAP took about 10 minutes on my free sunday evening, and another 30 minutes to make sure everything worked as i wanted to. (thanks to the nice tutorial on link i posted). In essence it was no more then right click -> convert.
It has all the new features the default webproject has, plus all the benefits of the more structured VS2003 webprojects ( no need for the web deployment projects, just 'publish' or create a web setup project..) And it works much faster (more of an issue when your projects grows and grows).
All in all we are very happy with the new WAP and i dont think we will ever use the old system again (unless we are forced to, or maybe join you bugnet project, and you refuse to upgrade ; ) ).
Anyway, try the current webproject, if you dont like it it's always possible to upgrade (it only takes 10 minutes of your fee sunday... :P) But dont say i didnt warn you ;).