That's what made me feel like a total clown. I normally test the hell out of my MSI's on my virtual machines by doing things like making "fake" future patches & upgrades to ensure they'll be fine if (when) we need to release an update in the future.
I guess you can't really know success until you've failed. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 04 March 2010 02:33 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating a Major Upgrade Patch On 3/3/2010 10:50 AM, Pally Sandher wrote: > Moral of the story, be absolutely certain when you're changing Product > Codes (still can't believe I made such an error, hoist by ones own > petard). > A higher-level moral: Test serviceability before shipping; afterward is too late to fix whole classes of bugs. (Heath, of course, is the ultimate source on the topic: http://blogs.msdn.com/heaths/archive/2010/02/14/serviceability.aspx .) -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
