Thanks…I needed it.

Thanks for this post. I was doing fine using the web site model but I wanted to put my source code into Visual Sourcesafe 2005 (Version 8.x) which prevented me from adding the web site because of the Front Page Server Extension files. For years, I have been using the WinDiff utility to compare ProductionWeb folders versus DevelopmentWeb folders and learning to visually ignore the inequalities in the _vti files.

So with the goal toward having all my web source under SourceSafe, I began an experiment of cloning/migrating my "web site" code into the "web application project" model – mostly to eliminate the requirement for FrontPage Server Extensions.

While I've achieved the SourceSafe objective, I have run into lots of confusion on the web application project way of doing things.

As I understand the web appl proj thing, all development is local and when I am ready I can copy a single DLL for my project to a remote IIS web server and hence FPSE will not be needed.

How do the experts handle minor changes then in their production web applications? If a minor change were required to some .ASPX markup, for example, would you have to FTP the new .ASPX file to the remote IIS server?

With the web site model, I could just edit the single file in place.

I guess a corallary question is could a web "site" model be placed under control of Visual Source Safe 2005 ?

De ahora en adelante [PLEFDS = para leer el fin de semana]. Digamos que hay dos maneras de tener el código

Pingback from  Visual Studio Team System  » Blog Archive   » ???????????? ?????? part 1.

Todo acerca de Inline, beside, behind, Web Site Project y Web Application Project. De ahora en adelante

Last week it was exactly one year since I started blogging, so this is my blog first birthday!! Come and read about the blog's statistics, top posts and more.

If you need the best performance in an application delivered to many users (7000 concurrent users), which project type is the best?

Regards.

Heidi

Hi Heidi

The web site – cause it’s compilation model.

I've searched the internet extensively looking for ANY information about a "Web application using multiple Web projects".  The only information that can be found is in articles just like this one that say to use a Web Application project.  What I want to know is this:

I have "web application" that consists of the web sites:  www, secure, and members.  The user browsers to a url at our domain and is directed to the www site where a login form exists on the home page.  The login form posts to the secure site where several checks are performed to verify the user is allowed to continue.  If the checks are passed the user is redirected to the members site where they can perform all kinds of tasks.  In VS 2003, we had 3 separate solutions, one for each of the sites.  The sites have common references to other assemblies.  So when I rebuild the members site, I also have to rebuild the www and secure sites just to make sure the referenced assemblies are all up to date.  I am now trying to create a solution that contains all three of the Web Application Projects as well as the referenced assemblies in VS 2008.  I am trying to find some information about how to make this work with the ASP.NET Development Server that is part of VS 2008 (if possible), recommendations about how to lay everything out in source control, and recommendations on setting up Team Project(s) in Team System for this.  

Any recommendations on where to find this kind of info?

Why is it's compilation model better than the compilation being done in a Web Application?

Regards,

Heidi