When to Deploy, when to change page

[wendas]

I am playing with Deploying using the Web setup Project. Any change I do this. I am told there is a time when you can just move in an altered page.

But, I am altering class libraries outside my project & rebuilding it, then rebuilding the project to take the change, Then rebuilding the Web setup.

For changes to the class libraries is this needed if the library change only effects one page? or will the rebuild of the project and an upload of the page to the website work? I guess if it effects multiple changes the rebuilding of the Web setup is still the best? Yes?

 

[jmeckley]

I assume web setup is like an msi package to deploy websites, correct? unless your deploying major enterprise level systems, why not just use xcopy/publish website. this is much simpler and you don't need to mess with install packages.

as for your question. this depend on what changed and how. If the public API changes then normally the client code calling the 3rd party assembly changes and thus both assemblies need to be updated.

if the internal objects (not exposed by the API) changes, then only that file needs to be updated, not the entire deployment.

As a safety measure, and for medium/small projects, just redeploy with each version. More time would probably be spent piece-mealing updates together rather than a complete overwrite.

Jason Meckley
Programmer
Specialty Bakers, Inc.