Re: Web site vs Web Application Project
- From: "Ray Costanzo" <my first name at lane 34 dot commercial>
- Date: Fri, 20 Apr 2007 07:41:11 -0400
I personally like that the SLN is elsewhere. When I setup projects in source control, I do not include the SLN file. To me, an SLN is a personal thing. When you're working on an application that has 30 projects, it should be up to each developer to create his own solution (or multiple solutions depending on which hat he's wearing that day) and just add the projects he needs from source control. Nothing's more annoying than working on a project with just 4 or 5 files, but having to open 30 projects to do so because of a communal SLN!
Ray at work
"Peter Bradley" <pbradley@xxxxxxxxxx> wrote in message news:eEbEv9zgHHA.4936@xxxxxxxxxxxxxxxxxxxxxxx
But...
In VS2005, if you create a new web site at the start of your project, VS2005 - in its wisdom - puts the solution file in a different file system tree from the project file. This makes a mess of source control if you're using VSS 6.0 or Subversion (so presumably CVS and many other source control sysems as well).
The solution is either to use the VS2003 Web application template; or (alternatively) to create a new, blank solution and to add a new Web site to the blank project. You then get everything in the "right" place (from my POV, anyway) i.e. with the project folders nested inside the solution folder.
Having to do this is a pain and is probably a major contributing reason as to why so many people yelled at MS until they put the Web application template back.
For the record, I create an blank solution and then add a VS2005 Web site to it - because I agree that in all other respects, VS2005 Web sites seem to be superior.
Peter
"Ray Costanzo" <my first name at lane 34 dot commercial> wrote in message news:7934192A-7ED5-4154-82B8-CB3224F6DF06@xxxxxxxxxxxxxxxxOriginally, Visual Studio 2005 did not offer a Web app project. The reason for this is that it was just a big PITA and totally illogical. When I first used VS2005 and saw this changed behavior in working with a Web site, I just about cried out in joy over this. To me, the whole Web app behavior in VS2003 was absolutely infuriating and totally asinine. But, here's (link below) a good breakdown of both options. Perhaps this is just because of a subconscious bias in my head, but I swear this article is rallying against the Web app project.
http://msdn2.microsoft.com/en-us/library/aa730880(vs.80).aspx
Ray at work
<nyhetsgrupper@xxxxxxxxx> wrote in message news:1177067039.591470.140120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxHi,
Which project type do you prefer? Is the web site or web application
project the best solution? The application I am about to write is
completly new so migrating from vs 2003 is not an issue, but it has to
be easy to deploy the application (precompiled, I don't want to give
away my source)
.
- Follow-Ups:
- Re: Web site vs Web Application Project
- From: Peter Bradley
- Re: Web site vs Web Application Project
- From: Mark Rae
- Re: Web site vs Web Application Project
- References:
- Web site vs Web Application Project
- From: nyhetsgrupper
- Re: Web site vs Web Application Project
- From: Peter Bradley
- Web site vs Web Application Project
- Prev by Date: Re: Web site vs Web Application Project
- Next by Date: Re: Listbox - identifying different values with a selected row
- Previous by thread: Re: Web site vs Web Application Project
- Next by thread: Re: Web site vs Web Application Project
- Index(es):
Relevant Pages
|