Lately I find myself using both
Web Application Projects and Web sites, depending on the project. I like the immediacy and simplicity of the Web site model, but I also find that having a real project file useful on occasions as well and end up using WAP for those situations (and definitely prefer WAP for migrating 2003 projects).
I really like the way WAP puts everything into a single directory, including the solution and project files - it's a huge improvement over how it used to work in 2003 (see my
work-around to the issues in 2003), not to mention the lack of dependency on IIS configuration.
Web sites are equally good in this respect, with one exception. When you create a new Web site, Visual Studio automatically creates and saves a solution file in your documents directory, which is of course never where I create my sites. So I use the following work-around when creating Web sites to get the same 'one directory' experience that WAP delivers:
- Create a new blank solution in Visual Studio in the directory of your choosing.
- Right click on the new solution in the Solution Explorer, and select 'Add | Existing Web Site…' and when presented with the file dialog, choose the same directory you chose for the initial solution (you can’t choose 'New Web site…' because it will complain that the directory is already populated).
- Voilà – a Web site with an accompanying solution file all in one self-contained directory!
Posted
Jan 03 2007, 09:40 AM
by
fritz-onion