Same as building an MSI.
On Fri, Dec 28, 2012 at 4:08 PM, gregbty wrote:
> Is there a list of the executables and dlls that are required for building
> the bundle?
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Editing-files-within-a-c
Is there a list of the executables and dlls that are required for building
the bundle?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Editing-files-within-a-compiled-bundle-tp7582554p7582571.html
Sent from the wix-users mailing list archive at Nab
You'd need to build the Bundles on the client side too. I'd say transforms
would be better than editing the MSIs but Burn doesn't handle transforms in
the chain, yet.
On Fri, Dec 28, 2012 at 2:04 PM, gregbty wrote:
> What does the Extension do?
>
> Let me a little context and maybe you can tell
What does the Extension do?
Let me a little context and maybe you can tell me if there is another way to
accomplish this. I have a central server application that is installed on a
Windows server machine. Inside of this application the user is able to
"build"
other installers for clients that
You might consider using an Extension instead of post processing the MSI.
Otherwise, build the bundle after tweaking the MSI.
On Thu, Dec 27, 2012 at 7:01 AM, Gregory Beaty wrote:
> In WiX 3.5 I was able to open a handle to the MSI, edit some internal user
> properties that I created during deve
In WiX 3.5 I was able to open a handle to the MSI, edit some internal user
properties that I created during development of the MSI, and save the MSI
with these updates. With WiX 3.6 the bundle that is created is a shell for
the internal MSI and other associated files for bootstrapping. Is there
any
6 matches
Mail list logo
