This sounds like a good way to start at least. My one concern is what happens when the accumulated patches start to get large enough to make size a concern? Lets say the original data is 2GB, and every month we need to release a patch that changes 5% of it. After 5 months we're up to a 500MB accumulated patch.
Would it be possible to release a small burn bootstrapper that detects which patches are installed and only downloads the ones that the user doesn't already have? Thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-strategy-tp7591585p7591600.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
