The upgrade path wouldn't concern me to much, because our end customer relationships are all 1-to-1. But you got me thinking with the signature part. Maybe my approach on this was not quite the best. Maybe I should consider just teaching my internal customer's how to make easy setup projects for pure configuration purposes. My installer application supports hierarchical binding of MSI packages anyway (kinda like features but with whole MSIs). So there even would be the possibility to just hook a new package below the one they want to configure.
Well I guess I'll go with that idea. Makes me feel more secure in this matter. :) Thank you guys for your help. PS.: If some other guy stumbles upon my initial problem, I kinda found a way to work that out: If you take the same-version-but-changed-package and call it with "REINSTALL=ALL" and "REINSTALLMODE=vomus" MSI will recache the MSI package instead of taking the one chached already. So that would have been a way. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
