Last post Mar 24, 2006 10:19 AM by razorphreak
Mar 21, 2006 05:49 PM|razorphreak|LINK
Mar 23, 2006 06:04 PM|ScottGu|LINK
In cases where you have sub-projects, I'd actually recommend using the new VS 2005 Web Application Project option (http://webproject.scottgu.com). It will make upgrading fairly straight-forward -- since it uses
a project file approach for references and can easily handle nested sub-projects.
We are going to have a feature complete version public on the web in about 2 weeks. If you want to send me email (firstname.lastname@example.org) I can also give you access to a near final build now. This should make it
easy for you to upgrade and not require code changes.
Hope this helps,
Mar 23, 2006 06:39 PM|razorphreak|LINK
Mar 23, 2006 10:05 PM|ScottGu|LINK
We are actually working on a whitepaper now that will help lay out some of the pros/cons of each approach and provide more guidance. The short answer is that it really depends on your development style/preference as well as how you want to structure your
code (so there isn't a right or wrong choice -- it really depends on how you want to work).
For cases like above where you are using sub-projects that make up a common application, I'd definitely recommend the VS 2005 Web Application Project approach -- since it is ideal for that case.
Mar 24, 2006 10:19 AM|razorphreak|LINK