WiX: .Net 3.5 prerequisite

Posted by Mike Pateras on Stack Overflow See other posts from Stack Overflow or by Mike Pateras
Published on 2010-03-29T22:10:36Z Indexed on 2010/03/29 22:13 UTC
Read the original article Hit count: 241

Filed under:

wix

|

bootsrapper

|

.NET

|

installer

|

msi

I have a WiX installer that I would like to check for .Net 3.5, and install it if it does not exist. I have the following lines in my wixproj file:

<BootstrapperFile Include="Microsoft.Net.Framework.3.5">
    <ProductName>.NET Framework 3.5</ProductName>
</BootstrapperFile>
<BootstrapperFile Include="Microsoft.Windows.Installer.3.1">
    <ProductName>WIndows Installer 3.1</ProductName>
</BootstrapperFile>

When I create the installer, a DotNetFX35 folder is created, and in it are 4 different versions of .Net (including 3.5), and an installer file.

I have two questions:

How do I have it only bring in version 3.5 (so that the user doesn't have to install 100+ MB of files)?
How do I tell WiX to package these files up into the MSI file, so that the user only has to download 1 file?

Related posts about wix

WiX 3: Using heat.exe to add bulk files to a new WiX project: HEAT5150

as seen on Stack Overflow - Search for 'Stack Overflow'
If this is a repeat question, please direct me to the existing solution. I wasn't able to find a matching query. We currently use InstallShield. I'm attempting to covert a project with 407 files to a WiX3 installation package. I tried using heat.exe to do some of the automation but I get the following… >>> More
Detect an Uninstall in a Launch Condition using Wix MSIs

as seen on Stack Overflow - Search for 'Stack Overflow'
I've been playing around with Wix, making a little app with auto-generated installer and three versions to test the upgradability, 1.0, 1.1 and 2.0. 1.1 is meant to be able to upgrade from 1.0, and not to allow the user to install 1.1 if 1.1 is already present. <Upgrade Id="F30C4129-F14E-43ee-BD5E-03AA89AD8E07"> … >>> More
How to modify IIS handler mapping permissions via Wix or a Custom Action

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi, I'm using Wix to create an installer for a Silverlight application. When I install the application the virtual directory that has been created has the execute permission checked for the *.dll handler mapping (IIS 7 Web site VDir Handler Mappings *.dll Edit Feature Permissions Execute)… >>> More
Wix XmlFile is keeping SqlDatabase from creating databases

as seen on Stack Overflow - Search for 'Stack Overflow'
I've got a Wix project made up of several fragments. One of those fragments has the database components, another has a component that manipulates xml files. When I include the XmlFile element to manipulate a file, the databases defined by the SqlDatabase do not get created. If I comment out the… >>> More
I'm referencing an WiX extension in a WiX library project -- how do I avoid having to reference this

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm referencing a WiX extension in a WiX library project. This WiX library project is itself referenced by my main WiX MSI project. Why does the main project have to also reference the WiX extension, even though it doesn't directly need it? I'd like to keep my wixlib's as self-contained as possible… >>> More

Developer IT

WiX: .Net 3.5 prerequisite - Developer IT

WiX: .Net 3.5 prerequisite

wix

bootsrapper

.NET

installer

msi

Related posts about wix

WiX 3: Using heat.exe to add bulk files to a new WiX project: HEAT5150

Detect an Uninstall in a Launch Condition using Wix MSIs

How to modify IIS handler mapping permissions via Wix or a Custom Action

Wix XmlFile is keeping SqlDatabase from creating databases

I'm referencing an WiX extension in a WiX library project -- how do I avoid having to reference this

Related posts about bootsrapper

WiX: .Net 3.5 prerequisite

Problems with Prism hosted in a WinForm ElementHost

Categories cloud