I want to be able to deploy a vs .net 2005 web application and make it so that we can drop a file in to patch say a coding defect.
What would be the best way to do this - currently we are not using web deployment projects and I believe our release team are precompiling the code befor eshipping it using wise installer.
I would rather not simply xcopy the files and welcome any suggestions.
If your release team is pre-compiling the web app before deployment, then the deployed files will be "pure binaries". In order to make your site updateable, you can create an assembly for each page using -fixednames compiler option. This way you have the
flexibility to update each single assembly, but this flexiblity comes at a price: you can have a large number of assemblies which might affect performance if there are many pages in your app.
Since you need to change the code-behind (to fix the coding defects), I think the only option you have is to update individual fixed named assemlies.
gsuttie2002
Contributor
2759 Points
655 Posts
Deploying a website to an environment in vs 2005 and making it patchable
Oct 29, 2006 07:29 PM|LINK
Hi Folks
I want to be able to deploy a vs .net 2005 web application and make it so that we can drop a file in to patch say a coding defect.
What would be the best way to do this - currently we are not using web deployment projects and I believe our release team are precompiling the code befor eshipping it using wise installer.
I would rather not simply xcopy the files and welcome any suggestions.
Thanks
Gregor
MCSD, MCAD, MCSD.Net
vivek_iit
All-Star
17778 Points
3189 Posts
MVP
Re: Deploying a website to an environment in vs 2005 and making it patchable
Oct 30, 2006 07:13 PM|LINK
Hi Gregor,
If your release team is pre-compiling the web app before deployment, then the deployed files will be "pure binaries". In order to make your site updateable, you can create an assembly for each page using -fixednames compiler option. This way you have the flexibility to update each single assembly, but this flexiblity comes at a price: you can have a large number of assemblies which might affect performance if there are many pages in your app.
Since you need to change the code-behind (to fix the coding defects), I think the only option you have is to update individual fixed named assemlies.
Hope this helps,
Vivek
Communifire: Social Networking and Business Collaboration Platform