Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
In the past, I've written a little bit about the packaging for the .NET Framework setup, including changes that have been made for the .NET Framework 2.0 (notably, the post here). I wanted to talk a little bit more about the underlying setup wrapper package and how it works. The setup wrapper is an MSI external UI handler that we specifically designed to be generic so that different types of MSI-based setup packages could use it. In fact, the same underlying wrapper is used to install the .NET Framework 2.0, the J# redistributable 2.0, the .NET Framework 2.0 SDK, .NET Framework and J# redistributable language packs, and a lot of the smaller MSI-based products that are a part of Visual Studio setup.
Let's take a quick look at the contents of the setup wrapper by downloading a build of the .NET Framework 2.0 (for example, from here). You'll see the following files:
Since this setup wrapper is designed to be generic, it can actually be used to install most MSI packages and not just the one it is packaged with. As an exercise, I decided to try to swap out the UI handler and use this setup wrapper to install the Orca MSI viewer/editor package. Here are the steps I took:
I will explore more details about this setup wrapper in a future blog post, including the following:
A while back, Quan To posted an item on his blog that briefly described a project he worked on to help
Question: I am building an MSI-based setup for my application. I would like the setup to contain UI strings
Reasons for setting ARPSYSTEMCOMPONENT to 1 despite the dangers.