Okay, so if we go back down to our component group, we'll see that the directory for that component group is install folder. So this will change to Wix Example Application. Program Files, or Program Filesx86, depending on whether you're running a 32 bit or a 64 bit machine, and then it's going to put it in an install folder. This is going to be the output directory structure, so it's going to actually install it in C which is this target DIR. So then we have a fragment with a directory structure. We're referencing the product components component group, which is down at line 23. Within our feature, we only have one thing, it's a component group reference. We'll leave this alone, but it's a pretty powerful tag as well. This is used down the road for determining if we want to install everything or only install application in central features versus documentation files. Media Template we're going to embed cab to “yes.” This is going to embed the cabinet file into the MSI so you only have one file to deliver to end users rather than two, two being your MSI and your cabinet file. This project name is a magic string which gets replaced with the name of your product, so Wix Installer. Major Upgrade: we're not going to mess with, but this default is preventing us from downgrading. Install Scope” I'm going to leave it as per machine, but you can switch this to per-user, depending the requirements of your application. Installer version, compressed, we can leave alone. Don't change this, if you ever want to upgrade, you'll need this exact good in order for it to upgrade, correctly at least.Īnd we have a package, we want to set the ID to be dynamic as well, by setting it to an asterisk. If we're installing Version 2 it's used to determine if Version 1 is installed or if Version 2 is the first installation of this application. Upgrade Code, this is a good which is used for upgrading. So the first thing we'll see is the product ID is set to an asterisk. Specifically, I want to add all the projects in my solution that I want to include in my installer.Ī way to do that is you right click, select add reference, go to projects, which is here, select all projects you want to include in the installer, add, okay, so now they're referenced, and then we can start messing with our xml. Select set-up project and we're going to call this Installer. We're going to select from the left-hand menu Windows Installer.xml. Hopefully you'll see a familiar window, the new project window. Right click on the solution, click add new project. So in order to get started with setting up our installer, we first want to go the solution explorer. Now we can get started on adding our installer. I have made the executable dependent on both the class library and the config file. There's also a class library called Wix Library. The executable has a config file and exe documentation file. I have created a very simple 'Hello World' application, called Wix Example Application. Once installed, launch Visual Studio, preferably with your project or solution open. To get started we first need to download and install the latest version of Wix from, which right now is at version 3.7. Today I'm going to go over the basic of Wix to get your started in creating custom installers for. My name is Spencer Glesmann, and I am a system's engineer at DMC. Welcome to this DMC video blog titled Wix Installer Tutorial for Visual Studio.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |