Sorry...my bad. It looks like you're using WiX 2.0. WiX
3.0/Votive is now producing MSBuild-based project files, which is how my script
below works.
It's been a while since I've used WiX 2.0. One option would be to create a
custom MSBuild script and include the bootstrapper tasks in that script. You
can then run that script after your installer is built to create the
bootstrapper program.
----------------------------------------
From: "Thomas Bjørnsen" <[EMAIL PROTECTED]>
Sent: Wednesday, April 18, 2007 6:15 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Forcing a .NET 2.0 install as a prerequisite
<?xml version="1.0" encoding="utf-8" ?>
<VisualStudioProject>
<WindowsInstallerXML
ProductVersion="2.0.4820.0"
ProjectGuid="{2BE447ED-089A-4AB2-826D-7BE4E037C7C7}"
SchemaVersion="1.0"
>
<BuildSettings
OutputName="Project"
OutputType="MSI"
/>
<Configurations>
<Configuration
Name="Debug"
RelativeOutputDirectory="bin\Debug"
RelativeIntermediateDirectory="obj\Debug"
/>
<Configuration
Name="Release"
RelativeOutputDirectory="bin\Release"
RelativeIntermediateDirectory="obj\Release"
/>
</Configurations>
<WixlibReferences />
<Files>
<File
RelativePath="Installer.wxs"
/>
<File
RelativePath="Files.wxs"
/>
</Files>
</WindowsInstallerXML>
</VisualStudioProject>
is my whole wixproj file, I don't seem to have the " Wix.targets" anywhere.
Installer.wxs is the main Wix file with the product, errormessages, actions
etc. Files.wxs is project spesific files (the components, linked mergefiles
etc). Don't quite see where i should add your XML nor how that would function?
Sincerely
Thomas
On 4/17/07, Michael Collins <[EMAIL PROTECTED]> wrote: I use the MSBuild
GenerateBootstrapper task to create a bootstrapper to install .NET 2.0, 3.0,
and other dependencies. It's fairly easy to add to your build process if
you're running MSBuild.
If you're using Votive, edit your .wixproj project file and add the following
code to the bottom of your .wixproj file, before and after it imports the
Wix.targets file.
<ItemGroup>
<BootstrapperItem Include=" Microsoft.Net.Framework.2.0">
<ProductName>Microsoft .NET Framework 2.0</ProductName>
</BootstrapperItem>
<BootstrapperItem Include="{511DAC48-6CBB-43a3-A64D-0182F2A9EBC2}">
<ProductName>Microsoft .NET Framework 3.0</ProductName>
</BootstrapperItem>
</ItemGroup>
<Target Name="GenerateBootstrapper">
<GenerateBootstrapper ApplicationName="My Application"
ApplicationFile="$(TargetFileName)" BootstrapperItems="@(BootstrapperItem)"
ComponentsLocation="HomeSite" OutputPath="$(OutputPath)" Culture="en-US" />
</Target>
<Import Project="$(WixToolPath)\Wix.targets" />
<PropertyGroup>
<BuildDependsOn>
PrepareForBuild;
Compile;
Link;
GenerateBootstrapper
</BuildDependsOn>
</PropertyGroup>
----------------------------------------
From: "Thomas Bjørnsen" <[EMAIL PROTECTED] >
Sent: Tuesday, April 17, 2007 6:43 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Forcing a .NET 2.0 install as a prerequisite
Is there any way to make WIX install .NET 2.0 if it doesn't find it (currently
i just check if it exists with a FileSearch to check mscoree.dll for version
2.0). I guess some kind of bootstrapper?
And if I want a feature to only install on windows 2k/XP is it enough to create
the feature and put a conditional OS Version check inside it? Will WIX install
multiple features even though the user doesn't have the option of touching
features (mainfeature + extrafeature for 2k/XP)?
Thx
-T
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
