Deployment of a VS2005 web application project

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.

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.

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.

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????

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.

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

Go for sp1 anyhow.
sp1 includes the webproject, is that the difference ?