tag:blogger.com,1999:blog-5274981767425509778.post5628922906368283441..comments2008-07-04T05:06:10.143+01:00Geert Verhoevenhttp://www.blogger.com/profile/04897992588367919830noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5274981767425509778.post-39614995602105798152008-07-03T21:33:00.000+01:002008-07-03T21:33:00.000+01:00Deployment of WebApplications is done using a 'Web Setup Project', which is probably more complicated than just copying the directory containing the application's files, but is usually worth it.<BR/><BR/>As Stéphane said, WebSite project is nice for ... web sites, not for enterprise web applications (that's why Microsoft reintroduced WebApplications in an emergency patch, even before the SP1 of VS2005). ;o)<BR/><BR/>Mastering your deployment phase is as important as mastering your development phase. That's why in Agile development, you release early & often. This will help ensure that you deployment process is fine tuned ... and you don't have bad surprises at the last minute.Stiiifffhttp://www.blogger.com/profile/15045429147976250345noreply@blogger.comtag:blogger.com,1999:blog-5274981767425509778.post-73728037440831662082008-07-03T21:11:00.000+01:002008-07-03T21:11:00.000+01:00I don't like the WebSite template either. Besides the issue I have here, I already had others in the past.<BR/><BR/>We need to use the WebSite template to avoid having different project types at the customer. Apparently they had issues with the deployment of WebApplications. Therefore we need to stick with the WebSite.Geert Verhoevenhttp://www.blogger.com/profile/04897992588367919830noreply@blogger.comtag:blogger.com,1999:blog-5274981767425509778.post-9073129173722531422008-07-03T20:03:00.000+01:002008-07-03T20:03:00.000+01:00Website are really painful to use in an enterprise environment. They are only convenient for small site or prove of concept.<BR/><BR/>Another annoying problem is related to the way files belong to a project. In fact, there is no project definition, all files which are in the folder are projects files. Normally you shouldn't put the bin directory under source control but if you don't do it others developers won't get your project references. <BR/><BR/>Maybe it's time to discuss with your customer ;-) InternalToVisible is a poor design choice to address this issue imho.<BR/><BR/>++ :-)Stéphanehttp://www.blogger.com/profile/01057471543030307997noreply@blogger.comtag:blogger.com,1999:blog-5274981767425509778.post-90388158499682689782008-07-03T08:14:00.000+01:002008-07-03T08:14:00.000+01:00On <A HREF="http://weblogs.asp.net/scottgu/archive/2006/07/30/Common-Gotcha_3A00_-Slow-VS-2005-Web-Site-Build-Performance-Because-of-_1C20_Dueling-Assembly-References_1D20_.aspx" REL="nofollow">Scott Guthrie's blog</A>, you can find another side effect of the behaviour of the website template which he calls “Dueling Assembly References”.Geert Verhoevenhttp://www.blogger.com/profile/04897992588367919830noreply@blogger.com