Peter's Gekko

public Blog MyNotepad : Imho { }

Deployment of a VS2005 web application project

With VS 2005 sp1 a web application project (which puts all webpages in a single assembly) is again a standard project type. What you have to watch yourself is the support in a deployment project. Having created a "web setup" project you see the folder tree on the target machine. This does include a bin folder.

It's up to you to include the right files in the right folders.

Content files in the root.
Primary project output and all loose referenced assemblies in the bin folder.

No big deal; but it's better to know this in advance instead of finding out behind your customers machine J

Published Dec 28 2006, 09:04 AM by pvanooijen

Filed under: ASP.NET

Comments

Gurjinder Singh Brar said:

Yes you are right. But I think in these days ‘Web site projects’ are easier to deploy than Web Application Projects. The only thing we need to do is ‘Publish Website’.

<br>

Thanks,

<br>

Gurjinder Singh Brar

<br>

<a href=http://agileguru.blogspot.com/>http://agileguru.blogspot.com/</a>

# December 29, 2006 2:06 AM

pvanooijen said:

Publish website only works when your dev machine has the right connection to the deployment target. In my case I only have a mailbox which acceprs msi's.

# December 29, 2006 4:11 AM

camera said:

Gurjinder is correct in stating the ease of deployment when the application supports one website. The problems I have with Web Site Projects are (1) when something doesn't deploy correctly, where should these files go? and (2) How do I deploy this solution on two, three, ten websites?

Web Application Projects allow me to develop one customizable solution and easily deploy it to multiple client sites. Apparently there are enough of us who like Web Application Projects that VS SP1 now bakes them in.

# January 2, 2007 8:32 AM

pvanooijen said:

It is easier to deploy _provided you have a connection to the target site_. Which will not be the case in most real-life scenarios.

Which files to copy where is not that difficult, you can use your local dev website as an example. Deploy the project output and redistribute it by hand over the foldertree as found in your dev-site.

The good thing about VS 2003 was that it did the latter automatically in the project template. Such a template should be made available for VS 2005.

# January 2, 2007 9:47 AM

Travich said:

Now if only I could get past the broken images and css files on my site.

I have literally been fighting this problem for weeks. The site uses Windows Auth and when I use other methods of Authentication, the images and CSS files appear/work.

Anybody have any ideas????

# January 23, 2007 1:02 AM

pvanooijen said:

That sounds like a rights question. Which account is requesting access to the css and images ? It will depend on the autentication mode used. You should be able to track this using one of the systinternals tools.

What should work always, is give everyone read access to the css and images, including their folder.

# January 24, 2007 4:25 AM

Senthilkumar said:

Is this true that the vs2005 sp1 has better deployment than VS2005 website publishing.i need a detail difference in these two deployments can any one elobarate on this

# April 27, 2007 9:18 AM