I was planning to use <PackageGroupRef Id="NetFx45Web"/> instead of <ExePackage ...>. Is that correct? And what do I put after the PackageGroupRef in the Chain so reference by product's installation? Do I have to create two separate projects in VS2012, one for the MSI and one for the bootstrapper? (Hopefully, not.)
-----Original Message----- From: Steven Ogilvie [mailto:steven.ogil...@titus.com] Sent: Monday, September 10, 2012 3:01 PM To: edandb...@breyfamily.net; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Tying .NET bootstrapper into existing WiX project I check for .NET4 FULL via this: <Chain> <ExePackage Id="DotNetFx40" DisplayName="Microsoft .NET Framework 4" SourceFile="..\PreReqs\dotNetFx40_Full_x86_x64.exe" InstallCommand="/passive /norestart" InstallCondition="Installed OR NETFRAMEWORK40FULL" Permanent="yes"/> Then I have this property: <Fragment Id="InstallConditionChecks"> <!-- Check for .NET 4.0 --> <PropertyRef Id="NETFRAMEWORK40FULL"/> This is in my bundle.wxs file (I am checking for .NET, SQLServer Express and 2 other prereqs :) Steve -----Original Message----- From: Ed and Beth Brey [mailto:edandb...@breyfamily.net] Sent: September-10-12 3:40 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Tying .NET bootstrapper into existing WiX project I have a run-of-the-mill .NET app with a simple existing WiX project. I'm trying to include Burn into the project to get the goodness of .NET framework bootstrapping. The app only needs .NET 4.0, so I'd like to install nothing if .NET 4.0 or 4.5 is present, or .NET 4.5 if neither are present (unless it's Windows XP, then NET 4.0, since 4.5 is not supported). The reason for installing 4.5 is just to avoid perturbing the user by installing an old version of the framework, which he'll probably someday have to upgrade. This seems like a fairly common scenario (except maybe the part about Windows XP, but support for XP could be dropped if it complicates things), but I can't find a good example that helps me put the whole thing together. In particular, it's not clear how the new <Bundle> element references the existing <Product> element. Does MsiPackage do this? If so, how? Thanks, Ed Brey ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
