ClickOnce or Upater Application block - which is best for deploying small changes?
Posted on 2007-10-12
I would like to deploy updates to a .Net 2.0 winforms VB application invisibly, easily, reliably and efficiently. Our application is fairly large with alot of minor changes going out to the field on a regular basis. Frequently we will need to replace several assemblies to react to compliance issues/modifications/new features, etc. Very infrequently will we need to redeploy the entire application.
Which technology is most efficient for patching in this way? ClickOnce or the Updater Application BlockVersion 2.0? Which technology will be most supported by MS? It looks like ClickOnce is the wave of the future....
My concerns are twofold --
1) Can ClickOnce be configured for a partial release of a large application (e.g. replace one assembly)?
2) If there are siginificant advantages to using the updater block... How difficult is it to setup and maintain the build code for the updater (e.g. we are a small shop and need to minimize time spent preping a release)? Can you give me a feel for the difference in labor involved for building a clickonce release vs an auto-updater release?