Ok
The line <WixVariable Id="WixStdbaLicenseRtf" Value="c:\<path>\License.rtf" />
is for including your own unique text on the install screen. For now I would
remove it and it will default to some other text. Once you get yours to
compile, you can then add in your own.
The second error I believe is because you are not including the WIX DLL's in
your VS2010 project. I believe you need to include WixBallExtension.dll,
WixNetFxExtension.dll and WixUIExtension.dll under references.
So how we have our project setup is below, the bottom 4 projects create a
single MSI, and then the top project takes that MSI along with several external
MSIs and combine them into a single Bundle.
So our Bundle.wxs is under BundleInstaller which is where we make reference to
the DLLs. The Bundle.wxs is the file I sent and one we/you are creating.
Solution
- BundledInstaller
- LaunchAppForm
- Loader
- Persistence
- PortalSetup
From: Vivek SOni [mailto:vivek.s...@brisetech.com]
Sent: Thursday, April 05, 2012 6:47 AM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Bind .msi file in .msi file
On 4/4/2012 7:17 PM, DuBois, Joseph wrote:
Sorry,
Hate to say I am not a WIX expert, the code I sent works for us, only changed
things to omit any sensitive data.
We are using Wix3.6(which is beta), so make sure you are using that. Also we
are using Visual Studio 2010 to build the final executable (installer).
So below is what I would start with given what you have supplied, the only
thing I am not 100% sure on is the c:\<path>\License.rtf, not sure if that is
unique to us or needed by Wix. Another developer (who has moved on) coded this
up originally so again it works for us. I got rid of the other stuff that I
know you do not need.
Below should install the two packages in order and force a reboot after the
second package is installed.
How to do check boxes and all, beyond my WIX expertise.
Hope this helps (guarantee no success over use of this code).
Joe
<?xml version="1.0" encoding="UTF-8"?>
<Wix
xmlns="http://schemas.microsoft.com/wix/2006/wi";<http://schemas.microsoft.com/wix/2006/wi>
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";<http://schemas.microsoft.com/wix/NetFxExtension>>
<Bundle Compressed="no" DisableModify="button" Version="1.0.0.0"
Manufacturer="Your company Name" Copyright="Your company Name"
UpgradeCode="de8cbfab-5f76-4ddb-b5fd-e946ea84f1ae" Name="Bundled Installer">
<BootstrapperApplicationRef
Id="WixStandardBootstrapperApplication.RtfLicense" />
<WixVariable Id="WixStdbaLicenseRtf" Value="c:\<path>\License.rtf" />
<Chain>
<MsiPackage Id="testDLG" SourceFile="c:\test_dlg.msi" Compressed="no"
EnableFeatureSelection="yes" Vital="yes">
<MsiProperty Name="ALLUSERS" Value="1"/>
</MsiPackage>
<MsiPackage Id="setup" SourceFile="c:\setup.msi" Compressed="no"
EnableFeatureSelection="yes" Vital="yes">
<MsiProperty Name="ALLUSERS" Value="1"/>
<MsiProperty Name="REBOOT" Value="force"/>
</MsiPackage>
<PackageGroupRef Id="Bundle.Generated.Packages"/>
</Chain>
</Bundle>
</Wix>
-----Original Message-----
From: Vivek SOni [mailto:vivek.s...@brisetech.com]
Sent: Wednesday, April 04, 2012 2:10 AM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Bind .msi file in .msi file
On 4/3/2012 6:38 PM, DuBois, Joseph wrote:
We were able to do this with the following.
The issue we ran into (that I posted a while back to the forums and never seen
an answer to) is that though anyone can uninstall the individual pieces only
the person who installed the "bundler" can uninstall it. And because the
bundler requires all the pieces to be uninstalled, if anyone uninstalls one of
them, it corrupts the bundler uninstall.
Hope this helps.
Joe
<?xml version="1.0" encoding="UTF-8"?> <Wix
xmlns="http://schemas.microsoft.com/wix/2006/wi";<http://schemas.microsoft.com/wix/2006/wi>
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExtension";<http://schemas.microsoft.com/wix/NetFxExtension>>
<Bundle Compressed="no" DisableModify="button" Version="1.0.0.0"
Manufacturer="company" Copyright="company"
UpgradeCode="de8cbfab-5f76-4ddb-b5fd-e946ea84f1ae" Name="Pedi Portal Bundled
Installer">
<BootstrapperApplicationRef
Id="WixStandardBootstrapperApplication.RtfLicense" />
<WixVariable Id="WixStdbaLicenseRtf" Value="c:\<path>\License.rtf" />
<WixVariable Id="WixStdbaLogo" Value="c:\<path>\pediLogo.png" />
<?define targetDomain = $(env.USERDOMAIN)?>
<Chain>
<ExePackage Id="DotNetFx4" InstallCondition="NETFRAMEWORK40CLIENT"
Protocol="netfx4" InstallCommand="/q /norestart /chainingpackage"
UninstallCommand="/q /norestart /chainingpackage" RepairCommand="/q /norestart
/chainingpackage" SourceFile="c:\<path>\dotNetFx40_Full_setup.exe"
Permanent="no" Compressed="no" Cache="no" Vital="no"></ExePackage>
<?ifdef $(var.Platform)=x64) ?>
<MsiPackage Id="PediPortal" SourceFile="C:\<path>\PortalSetup.msi"
Compressed="no" EnableFeatureSelection="no" Vital="yes">
<MsiProperty Name="ALLUSERS" Value="1"/>
</MsiPackage>
<?else?>
<MsiPackage Id="PediPortal" SourceFile="C:\<path>\PortalSetup.msi"
Compressed="no" EnableFeatureSelection="no" Vital="yes">
<MsiProperty Name="ALLUSERS" Value="1"/>
</MsiPackage>
<?endif?>
<MsiPackage Id="ImprivataCHB" SourceFile="c:\<path>\second.msi"
Compressed="no" EnableFeatureSelection="yes" Vital="yes">
<MsiProperty Name="ALLUSERS" Value="1"/>
<MsiProperty Name="REBOOT" Value="force"/>
<MsiProperty Name="AGENTTYPE" Value="1"/>
</MsiPackage>
<PackageGroupRef Id="Bundle.Generated.Packages"/>
</Chain>
</Bundle>
</Wix>
-----Original Message-----
From: Vivek SOni [mailto:vivek.s...@brisetech.com]
Sent: Tuesday, April 03, 2012 5:34 AM
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: [WiX-devs] Bind .msi file in .msi file
Hello Everybody,
Actually I want to know that "can I bind a .msi file in another .msi file?" If
yes then please help me to do this as I am new on WIX, I don't have much idea
about this. Thanks in advance.
----------------------------------------------------------------------
-------- Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second resolution app
monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
----------------------------------------------------------------------
-------- Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second resolution
app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
Thanks Joe,
Actually I was getting an error while implementing that code sent by You. The
error is "The element in 'Wix' namespace
"http://schemas.microsoft.com/wix/2006/wi";<http://schemas.microsoft.com/wix/2006/wi>
has invalid child element 'Bunlde' ". So can You please tell me the solution
of this error.
Suppose I have to bind two msi file named "test_dlg.msi" and setup.msi .
The path of both the files are C:\test_dlg and C:\setup.msi . So Please send me
a code which bind both the files.
One more thing I want to Launch this msi file with checkbox. Suppose I check
any checkbox, it should install setup.msi . Please tell me how to implement
this also.
--
Vivek Soni
vivek.s...@brisetech.com<mailto:vivek.s...@brisetech.com>
+91-7877127178
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
.
Hello Joe,
When I upgraded my Wix version 3.5 to 3.6, the error "The element in 'Wix'
namespace "http://schemas.microsoft.com/wix/2006/wi"; has invalid child element
'Bunlde' " is removed.
But some another error are coming again:First one is Error 2 Unresolved
reference to symbol
'WixBootstrapperApplication:WixStandardBootstrapperApplication.RtfLicense' in
section 'Bundle'
and second one is Error 3 Unresolved reference to symbol
'ChainPackageGroup:Bundle.Generated.Packages' in section 'Bundle'.
I am searching about this from last couple of hours but haven't found the
solution. Do you have any idea about these error.
I have implemented the same code sent by you but it's also throwing the same
error. I am using Wix 3.6 and Visual Studio 2010.
--
Vivek Soni
vivek.s...@brisetech.com<mailto:vivek.s...@brisetech.com>
+91-7877127178
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
