Funny thing about ClickOnce is that it has very similar Component Rules in it (a little more flexible with the version) but still very restrictive. People don't see it because the standard use for ClickOnce is very much like "major upgrades" using new root directories every time. Works fine for small applications... just like MSI does with major upgrades.
Thinking about ClickOnce just makes me sad. So much time wasted creating a new solution with the exact same weaknesses. "But it should just be xcopy!" <sigh/> -----Original Message----- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Tuesday, December 30, 2008 10:21 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WIX 3 - Suggestions John Robbins wrote: > I can't help but think that it sounds like the whole patching system in > Windows Installer is not really a viable solution for the real world. Bummer. > Hmmm...If all of software were easy, there'd be little room for some of us to provide "consulting & debugging and training," would there?<g> Seriously, while it's a design that's forced on us, it's no different than any other time we've been contorted by forces outside our control. Where's the CLR equivalent of a setup engine? Well, they gave us ClickOnce, didn't they? Er, never mind.<g> I suspect too few of the TPTB are ready to invest in a solution; it's not a minor fix to MSI but a replacement engine. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
