Comments on: Auto-update with WiX

By: Victor Sergienko

Victor Sergienko — Fri, 21 Mar 2008 08:21:28 +0000

Thank you.

I already came with own solution based on Updater 2 Application Block, will blog what I’m allowed to later.

I knew that thing about Advertise, it’s another example of complexity that wrapper should hide.

By: guest

guest — Fri, 21 Mar 2008 08:18:46 +0000

Other solution would be to use ClickOnce to deploy a package that consists of your own code to perform all service tasks related to upgrade along with MSP itself. This model is far from perfect, of course, starting from deploying and installing your own certificate, which expires one day, taking care of security and other crap…

P.S. If you can’t create a Program Menu shortcut, make sure you set “Advertise” property correctly for your shortcut.

By: Victor Sergienko

Victor Sergienko — Wed, 19 Mar 2008 16:39:05 +0000

Hi Ewart,
ClickThrough is not only limited in docs (”source is the doc”), but the source is incomplete and hardly functional. For now it is GOING to support only SmartClient and Office addon deployment.

The only nearly-working thing I found is Updater appblock. It’s well-designed and mostly functional, though I had to hack out all EntLib dependencies

I’ll blog about it in more detail when we’re done with the release I’m trying to install.

By: Victor Sergienko

Victor Sergienko — Wed, 19 Mar 2008 16:20:19 +0000

Thanks Wladimir, I just saw that only thing it has that I need - is a download() function in API - and decided I’d stick to more conventional do-it-yourself kits, like WiX.

By: Ewart

Ewart — Sat, 15 Mar 2008 03:20:23 +0000

Would be interested to hear how your auto-update solution works out, was about to look at wix ClickThrough myself… there seems to be limited doc’s.

cheers
ewart

By: Wladimir Mutel

Wladimir Mutel — Fri, 14 Mar 2008 07:13:35 +0000

NSIS is a pain as well, from my experience. Like to write in assembler for a weird virtual machine ? Go ahead :>