Be aware, if you write those values back into the MSI, then you just invalidated the digital signature. The MSI will have to be re-signed.
MSI is just a database, so you can easily write a script to update it. You can also edit the MSI with Orca (or my favorite, InstEd). Now the (weird) thing to consider. What happens when an end customer gets our package from middleman-1 and then gets an upgrade (or same version) from middleman-2? That would be a weird upgrade path as far as the user is concerned... Dave >________________________________ > From: fom Forstner Michael <f...@keba.com> >To: General discussion about the WiX toolset. ><wix-users@lists.sourceforge.net> >Sent: Friday, March 7, 2014 4:30 PM >Subject: Re: [WiX-users] Running an MSI twice > > >Unfortunately not. >The idea is that I deliver a base version of a product. >My internal customers can add some configuration commands on their own. >Now, if they want to change the configuration commands they use my program and >change the related propery in the MSI. >Then they deliver it to the end customer, which just deploys the new package >to their machines. The new package is called and a upgrade should happen. >Unfortunately no user input is possible in my scenario. > >kind regards > > ------------------------------------------------------------------------------ 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
