I did something like this for one of my customers. He had value added resellers that would inject custom files and metadata / rebranding it. The end user sysadmins would then make additional tweaks before distributing across the enterprise. Each layer could then "seal" certain attributes so that the next person transforming the installer had less choices.
He wrote the UI wizard and I wrote the "InstallTransformer" class library. It was kind of fun and I could be convinced to share snippets for the who need it. ---------------------------------------- From: "Bas Graaf" <bas.gr...@microsoft.com> Sent: Friday, November 01, 2013 5:27 PM To: "General discussion about the WiX toolset." <wix-users@lists.sourceforge.net> Subject: Re: [WiX-users] Adding files to msi Yes, we considered giving them our source also. However, we'd like to keep it as simple as possible (for them). Typically, they would not know anything about WiX or Windows Installer internals and our WiX source is quite complicated. Although the wixlib suggestion would at least not expose them to that. I'll include it in my investigations. Thanks for the suggestion. _Bas -----Original Message----- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: 1. november 2013 23:07 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Adding files to msi 2013/11/1 Bas Graaf <bas.gr...@microsoft.com>: > Hi, > > I'd like to enable our partners to simply add a few files to our installer > package (an msi) before they deliver it to their customers (e.g., to add > third-party plugins, certificates, and various other configuration files). > So far, I've been prototyping a simple tool based on DTF to add relevant > records to the msi database. This seems to work fine. All that is left is to > add the actual file(s) to the embedded cab. I tried > InstallPackage.UpdateFiles, but this only seems to update files that were in > the cab before. > > Next idea is to get the cab from the _Streams table, add files, and put it > back. Just wanted to check here if there is anything in DTF (or elsewhere) > that already implements such a scenario. That sounds quite nasty. Why don't you give them your WiX source for them to modify and rebuild, or a wixlib they can include in their own package? -- Nicolás ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
