I have the following fragment:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;Wix xmlns=&quot;http://schemas.microsoft.com/wix/2006/wi&quot;&gt;
        &lt;Fragment&gt;
            &lt;ComponentGroup Id=&quot;Doc&quot;&gt;
                &lt;ComponentRef Id=&quot;cmpCDCC386748AE7BEFE7C2F4E764390254&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmp6EC513AE37CCAE66CEA96577E2384AFA&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmp0C9D9450CB94FF74C6E29C1C3F6D16D5&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmp314DEE3E909157F47FDF963DCC04D2AC&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmpBC5FB761D7B0DA99F96ECA9A91DD4217&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmp6B9E4B7B6F710D7077171BCE0B96A90A&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmp5959CF1572C71417D536C491A996C6DE&quot; /&gt;
                &lt;ComponentRef Id=&quot;cmpCC960E9F3DDDE1600206003C43FFE663&quot; /&gt;
            &lt;/ComponentGroup&gt;
        &lt;/Fragment&gt;
        &lt;Fragment&gt;
            &lt;DirectoryRef Id=&quot;AzureApplicationSDK&quot;&gt;
                &lt;Directory Id=&quot;dir67745C9C3FA1B31D9AF8883D12D8FBD8&quot; Name=&quot;Doc&quot;&gt;
                    &lt;Component Id=&quot;cmpCDCC386748AE7BEFE7C2F4E764390254&quot; Guid=&quot;{A46C5689-42D1-41CA-AD71-B2A416FA9571}&quot;&gt;
                        &lt;File Id=&quot;fil3B7DFCD3444314759F8617411F7EE08C&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Azure Applications SDK v1 Cascade Tables Getting Started Guide.docx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmp6EC513AE37CCAE66CEA96577E2384AFA&quot; Guid=&quot;{697C1B04-5279-4B31-9600-F3BCA4C1AD06}&quot;&gt;
                        &lt;File Id=&quot;filFDDD2C48EF5C14BA924C4272E4D9D490&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Azurite Identity.docx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmp0C9D9450CB94FF74C6E29C1C3F6D16D5&quot; Guid=&quot;{1C61C6C5-60F0-41A5-B229-093419E5F767}&quot;&gt;
                        &lt;File Id=&quot;fil4C736D0525C45780C242DA3BCA6823BA&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Mercurius messaging how-to.docx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmp314DEE3E909157F47FDF963DCC04D2AC&quot; Guid=&quot;{FD9BD847-5B89-42EA-A178-451AC8B822F4}&quot;&gt;
                        &lt;File Id=&quot;fil841FCFCD72670AEF83A89B6724126546&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Nexus Notes.pptx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmpBC5FB761D7B0DA99F96ECA9A91DD4217&quot; Guid=&quot;{2424B541-D40B-4D2D-938E-0AC5C9C2A773}&quot;&gt;
                        &lt;File Id=&quot;fil8D9E68E77FC45E6F50191FF6F20F2039&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Owner Powershell Snapin.docx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmp6B9E4B7B6F710D7077171BCE0B96A90A&quot; Guid=&quot;{E467FD03-EFB4-4E4F-9A34-75540BEB1B1C}&quot;&gt;
                        &lt;File Id=&quot;filB48A598247AE4A63638F96A69A545EE4&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\SDK First Look.pptx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmp5959CF1572C71417D536C491A996C6DE&quot; Guid=&quot;{27890FBC-2822-4061-A086-E9E539F58A64}&quot;&gt;
                        &lt;File Id=&quot;fil9CCA5FE9338BD9EB6E1E2B4F685D9F16&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Unit Tests.docx&quot; /&gt;
                    &lt;/Component&gt;
                    &lt;Component Id=&quot;cmpCC960E9F3DDDE1600206003C43FFE663&quot; Guid=&quot;{D9B8BFB9-3F3B-40FE-A3E9-C5E1669E529A}&quot;&gt;
                        &lt;File Id=&quot;fil98D1506B9A1C3AD2D9D03EA43BEEB80A&quot; KeyPath=&quot;yes&quot; Source=&quot;SourceDir\Using Nexus.docx&quot; /&gt;
                    &lt;/Component&gt;
                &lt;/Directory&gt;
            &lt;/DirectoryRef&gt;
        &lt;/Fragment&gt;
    &lt;/Wix&gt;

Within my main .wxs file I have the following:

    &lt;Feature Id=&quot;MainApplication&quot; Title=&quot;zure Application SDK&quot; Level=&quot;1&quot;&gt;
        &lt;ComponentRef Id=&quot;Doc&quot;/&gt;
    &lt;/Feature&gt;


I execute 

    C:\Program Files (x86)\Windows Installer XML v3\bin\Light.exe -cultures:null -ext &quot;C:\Program Files (x86)\Windows Installer XML v3\bin\WixUIExtension.dll&quot; -ext &quot;C:\Program Files (x86)\Windows Installer XML v3\bin\WixNetFxExtension.dll&quot; -out &quot;c:\source\Azure Applications SDK\Bespin\QADrop\QADropInstaller\bin\Release\QADropInstaller.msi&quot; -pdbout &quot;c:\source\Azure Applications SDK\Bespin\QADrop\QADropInstaller\bin\Release\QADropInstaller.wixpdb&quot; -v obj\Release\QADropInstall.wixobj obj\Release\Doc.wixobj 

and I get the following error 

    Error	21	Unresolved reference to symbol &#39;Component:Doc&#39; in 
    section &#39;Product:{CF56D65B-BE0D-4719-BEFD-5DC04F7AD7FC}&#39;.	
    c:\source\Azure Applications SDK\Bespin\QADrop\QADropInstaller\QADropInstall.wxs
    160	1	Azure Application SDK Installer

Can anyone tell me what I&#39;m doing wrong?






How to include Wix Fragments created by Heat

We decided to switch from VS integrated setup to WiX.

However, what we currently do is use projects output files as the input for the setup project. This lets us easily add Application Files to a directory (for images, samples, and other resources...) and those files are automatically added to the setup when we build.

I could not find any similar feature in WiX. WiX seems to require one Directory entry and one File entry for each and every directory and file. This would require us to change the WiX source everytime a file is added which, to my eyes, is prohibitive since we have so many of them.

Is there any integrated way of doing that with WiX or do I have to write my own task that will create a WiX source before calling candle?

How to add a whole directory or project output to WiX package

I&#39;m starting to use WiX in order to do automated builds to create msi&#39;s of my c# projects and am experiencing the error **&quot;Undefined preprocessor variable &#39;$(var.MyProject.TargetDir)&#39;&quot;**

I am using the latest WiX v3.0.5419. Inside my wxs file I am trying to use pre-processor variables that are listed on this webpage ([**http://blogs.msdn.com/jrock/archive/2008/01/29/complete-list-of-candle-preprocessor-variables.aspx**][1])

    &lt;Component Id=&quot;MyId&quot; Guid=&quot;MyGuid&quot;&gt;
       &lt;File Id=&quot;MyId&quot; Name=&quot;MyName&quot; KeyPath=&quot;yes&quot; 
          Source=&quot;$(var.MyProject.TargetDir)\MyName.dll&quot; /&gt;
    &lt;/Component&gt;

I have added the reference for MyProject to the .wixproj and if I open it up in Notepad I can see the reference.

    &lt;ItemGroup&gt;
      &lt;ProjectReference Include=&quot;..\MyProject.csproj&quot;&gt;
        &lt;Name&gt;MyProject&lt;/Name&gt;
        &lt;Project&gt;{guid}&lt;/Project&gt;
        &lt;Private&gt;True&lt;/Private&gt;
      &lt;/ProjectReference&gt;
    &lt;/ItemGroup&gt;

This is my nant build script that I use to create the msi. Maybe it&#39;s because the .wixproj knows about the project reference which isn&#39;t used in the build?

    &lt;exec basedir=&quot;${tools.wix}&quot; managed=&quot;true&quot; program=&quot;candle.exe&quot;&gt;
      &lt;arg line=&#39;-out &quot;${tools.wix.objfile}&quot;&#39; /&gt;
      &lt;arg value=&quot;../MySetup.wxs&quot; /&gt;
    &lt;/exec&gt;

Can anyone enlighten me on this please?

  [1]: http://blogs.msdn.com/jrock/archive/2008/01/29/complete-list-of-candle-preprocessor-variables.aspx

WiX undefined preprocessor variable

I&#39;m comparing these two tools.  The impression I have is:

* Inno Setup does not produce an MSI, but can do everything WIX can do
* WIX does produce an MSI, but has a steep learning curve

Do you agree with this characterization?  What other differences are there?  How does [WIX#][1] shake-up this story?  Since Inno Setup does not use the windows installer, does it have difficulty with uninstalls?  Can Inno Setup, upon command, downgrade an installation to an earlier version - or can it only install / upgrade applications?


  [1]: http://www.codeproject.com/KB/install/WixSharpArticle.aspx

Installers: WIX or Inno Setup?

We&#39;ve been using WiX for a while now, and despite the usual gripes about ease of use, it&#39;s going reasonably well. What I&#39;m looking for is useful advice regarding:

 - Setting up a WiX project (layout, references, file patterns)
 - Integrating WiX into solutions, and build/release processes
 - Configuring installers for new installations and upgrades
 - Any good WiX hacks you&#39;d like to share


WiX tricks and tips

At work we use [WiX][1] for building installation packages. We want that installation of product X would result in uninstall of the previous version of that product on that machine.

I&#39;ve read on several places on the Internet about a major upgrade but couldn&#39;t get it to work.
Can anyone please specify the exact steps that I need to take to add uninstall previous version feature to WiX?

  [1]: http://en.wikipedia.org/wiki/WiX


How to implement WiX installer upgrade?

My Wix project creates install.msi and cab1.cab. How can I have it bundle everything into the msi? I will likely use 7-zip SFX to work around this but I have seen other apps with only a single msi.

Wix: single MSI instead of msi + cab

I would like to modify an MSI installer (created through [WiX][1]) to delete an entire directory on uninstall.

I understand the `RemoveFile` and `RemoveFolder` options in WiX, but these are not robust enough to recursively delete an entire folder that has content created after the installation.

I noticed the similar Stack Overflow question *[Removing files when uninstalling WiX][2]*, but I was wondering if this could be done more simply using a call to a batch script to delete the folder.

This is my first time using WiX, and I&#39;m still getting the hang of [custom actions][3]. What would be a basic example of a custom action that will run a batch script on uninstall?

  [1]: http://en.wikipedia.org/wiki/WiX
  [2]: https://stackoverflow.com/questions/195919
  [3]: http://wix.sourceforge.net/manual-wix2/authoring_custom_actions.htm


How to add a WiX custom action that happens only on uninstall (via MSI)?

I wrote an application and its WiX installer and put it under version control using subversion. When the WiX installer builds I want its version number to be the current build version of the application. How do I accomplish this? I used c# to code the application.

N.B. I am using ccnet to build this project

How can I set the WiX installer version to the current build version?

What is the Wix &#39;**KeyPath**&#39; attribute? In particular, how does it apply to the following:

&lt;!-- language: xml --&gt;

    &lt;Component Id=&quot;ProgramMenuDir&quot; Guid=&quot;*&quot;&gt;
      &lt;RemoveFolder Id=&quot;ProgramMenuDir&quot; On=&quot;uninstall&quot; /&gt;
      &lt;RegistryValue Root=&quot;HKCU&quot; Key=&quot;Software\CompName\AppName&quot; 
                     Type=&quot;string&quot; Value=&quot;&quot; KeyPath=&quot;yes&quot; /&gt;
    &lt;/Component&gt;



What is the wix &#39;KeyPath&#39; attribute?

When I go the the New Project dialog in Visual Studio 2015, Windows Installer XML isn&#39;t available. How can I enable WiX projects in Visual Studio 2015?

How to Enable WiX Projects in Visual Studio 2015

I have a MSI package that I need to install if the package is not already installed. Also I need to install it silently. The package prompts user for:

- Installation location (C:\Program Files\Foobar\)
- Install type: minimal and full (minimal)

I need to override these two parameters using command line parameters or some other method. So how do I go about these two issues. I&#39;ll use VBScript for scripting.

Silent installation of a MSI package

I have a VS 2012 solution with WiX Installer projects. However, when I open the solution in VS 2013 (Release) the WiX project is incompatible.

Does anyone know where / whether a VS 2013 version (wixtoolset ?) is available being worked on yet? Or is there a way to make the current project compatible in VS 2013?

Enable WiX project in Visual Studio 2013

When uninstalling my application, I&#39;d like to configure the [Wix][1] setup to remove all the files that were added **after the original installation**. It seems like the uninstaller removes only the directories and files that were originally installed from the MSI file and it leaves everything else that was added later in the application folder. In another words, I&#39;d like to purge the directory when uninstalling. How do I do that?

  [1]: http://en.wikipedia.org/wiki/WiX


Removing files when uninstalling WiX

I&#39;ve given up trying to apply lipstick to the pigs of installers that come out of [Visual Studio][1] and have decided to look at [WiX][2].

What resources would you recommend to learn and reference?

*(Note - this is not a which-installer-technology-do-you-use question - it&#39;s specific to WiX.)*

  [1]: http://en.wikipedia.org/wiki/Microsoft_Visual_Studio
  [2]: http://en.wikipedia.org/wiki/WiX


Good resources for learning how to create MSI installers from WiX

I&#39;m trying to parse some XML inside a WiX installer. The XML would be an object of all my errors returned from a web server. I&#39;m getting the error in the question title with this code:

    XmlDocument xml = new XmlDocument();
    try
    {
    	xml.LoadXml(myString);
    }
    catch (Exception ex)
    {
    	System.IO.File.WriteAllText(@&quot;C:\text.txt&quot;, myString + &quot;\r\n\r\n&quot; + ex.Message);
    	throw ex;
    }

`myString` is this (as seen in the output of `text.txt`)

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;Errors&gt;&lt;/Errors&gt;

`text.txt` comes out looking like this:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;Errors&gt;&lt;/Errors&gt;
    
    Data at the root level is invalid. Line 1, position 1.

I need this XML to parse so I can see if I had any errors.

xml.LoadData - Data at the root level is invalid. Line 1, position 1

I need to find the **product GUID** for an **installed MSI file** in order to perform maintenance such as **`patching`**, **`uninstall`** ([**how-to uninstall**][1]) and also for **`auditing purposes`**.

  [1]: https://stackoverflow.com/questions/450027/uninstalling-an-msi-file-from-the-command-line-without-using-msiexec/1055933#1055933

How can I find the product GUID of an installed MSI setup?

In WIX, how do you create a non advertised shortcut in the allusers profile?  So far I&#39;ve only been able to accomplish this with advertised shortcuts.  I prefer non-advertised shortcuts because you can go to the shortcut&#39;s properties and use &quot;find target&quot;.

In the tutorials I&#39;ve seen use a registry value for the keypath of a shortcut.  The problem is they use HKCU as the root.  When HKCU is used, and another user uninstalls the program (since it&#39;s installed for all users) the registry key is left behind.  When I use HKMU as the root I get an ICE57 error, but the key is removed when another user uninstalls the program.  I seem to be pushed towards using HKCU though HKMU seems to behave correctly (per-user vs all-users).

When I try to create the non advertised shortcut I get various ICE error such as ICE38, ICE43, or ICE 57.  Most articles I&#39;ve seen recommend &quot;just ignore the ice errors&quot;.  There must be a way to create the non advertised shortcuts, without creating ICE errors.

Please post sample code for a working example.

Wix create non advertised shortcut for all users / per machine

I&#39;m currently doing some investigation on moving off of the installation package we currently use (Wise Installer 9) and moving to something that will handle things like Windows Vista, Windows&amp;nbsp;7 and 64-bit systems. Localization of the installers would be of benefit since we do have a number of French Canadian clients as well.

We currently have installations for software packages and utilities in the following technologies:

- Progress 4GL
- Visual Studio 2005
- Visual Studio 2008
- .NET Compact Framework 3.5

I&#39;ve already looked at [WiX][1] and [InstallShield][2], and also the [Altiris made replacement][3] for the old Wise system.

I haven&#39;t played with InstallShield much at all yet, but from everything I&#39;ve seen/installed it seems to be one of the industry favourites. I&#39;ve browsed through some of the Stack Overflow tags relating to [InstallShield][4] and I&#39;m curious to see what the group says about it.

Do I just by default go to them? How good is WiX at non-.NET stuff?

  [1]: http://wix.sourceforge.net/
  [2]: http://www.acresso.com/products/is/installshield-overview.htm
  [3]: http://www.symantec.com/business/wise-installation-studio
  [4]: http://en.wikipedia.org/wiki/InstallShield


What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc

I would like to use the WixUI_Minimal installer, but I don&#39;t want the license page. How can I do this?


How to build a minimal WiX installer UI without a license page?

I wrote an install program with Wix and it worked fine to install my program.
Now I need to update it, so I bumped up the version number but when I go to install the new program over the old one it complains that an older version is already installed and tells me to uninstall it first.

How do I get it to update or automatically uninstall it before reinstalling?

How to get Wix to update a previously installed version of a program

This is the error that is thrown by our automated build suite on Windows 2008, while running [ICEs][1] (after migrating from [WiX][2] 2.0 to WiX 3.0):

&gt; LGHT0217: Error executing ICE action &#39;ICE01&#39;. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: &quot;The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.&quot;. in light.exe(0, 0)

Additionally, these are the errors that show up in the event log:

&gt; MSIInstaller: Failed to connect to server. Error: 0x80070005
&gt; Product: [ProductName] -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

Intuitively:

* [VBScript][3] and [JScript][4] were registered under admin.
* Integration service has permissions for the desktop interaction and all the files
* Builds succeed, when executed manually on the same machine by another user or even user logged in as integration account (via [RDP][5])

I&#39;m out of ideas so far.

**How do I solve this problem while keeping ICE validation?**

  [1]: http://msdn.microsoft.com/en-us/library/windows/desktop/aa369554%28v=vs.85%29.aspx
  [2]: http://en.wikipedia.org/wiki/WiX
  [3]: http://en.wikipedia.org/wiki/VBScript
  [4]: http://en.wikipedia.org/wiki/JScript
  [5]: http://en.wikipedia.org/wiki/Remote_Desktop_Protocol


WiX 3.0 throws error 217, while being executed by continuous integration

When installing Windows services there are two options for automatically starting a Windows service on Windows startup. One is *Automatic*, and the other is *Automatic (Delayed start)*. What is the difference between these two in detail?

For example, if you&#39;re creating the installer with wixtoolset, the `ServiceConfig` element has the `DelayedAutoStart` attribute. How will that effect what happens when services are started at boot time?

WiX documentation: *[ServiceConfig Element][1]*

  [1]: http://wixtoolset.org/documentation/manual/v3/xsd/wix/serviceconfig.html



&quot;Automatic&quot; vs &quot;Automatic (Delayed start)&quot;

I&#39;m need to choose a software package for installing software. NSIS and WiX seem promising. Which one would you recommend over the other and why?

Feel free to offer something else if you think it&#39;s better than these two.


Free software for Windows installers: NSIS vs. WiX?

`msiexec` is command prompt software that installs an [MSI][1] program. But I have found that you can install an MSI file from the command line by just typing in the name of the MSI file on the command line.

But in order to uninstall the MSI file, it seems you have to call the `msiexec` program and give it a `/x` or `/uninstall`.

How can I uninstall an MSI from the command line without using the `msiexec` routine?

  [1]: http://en.wikipedia.org/wiki/Windows_Installer


Uninstalling an MSI file from the command line without using msiexec

Should I wrap all the files I want to install in individual components?
What is the advantage of putting several files in one component?


One file per component or several files per component?

WiX files always seem to include this line:

    &lt;Directory Id=&quot;TARGETDIR&quot; Name=&quot;SourceDir&quot;&gt;

What is &quot;SourceDir&quot;? What is it used for? It&#39;s not a real directory name. Is it some kind of magical value?


In WiX files, what does Name=&quot;SourceDir&quot; refer to?

How are properties set on [CustomActionData][1] to be retrieved by a deferred custom action?

  [1]: http://msdn.microsoft.com/en-us/library/2w2fhwzz%28v=vs.80%29.aspx


How to pass CustomActionData to a CustomAction using WiX?

I&#39;m having some strange issues with WiX on my local machine. The problem is intermittent, but after a few rebuilds of the solution, the WiX project starts throwing ICE validation errors.

If I go into my `AppData\Local\Temp` folder and delete all the temporary folders that contain the MSI, the solution compiles again. A short while later, the problem starts happening again. Having to keep clearing down the temp folders isn&#39;t a sustainable or satisfactory solution.

Has anyone else encountered this issue? The validation error codes seem to always be a combination of ICE30, ICE38, ICE64 and ICE91

Update:

As requested, here are the entries from the most recent failure:&lt;br&gt;

&gt; error LGHT0204: ICE38: ICE Internal Error 1002. API Returned:
&gt; 1615.&lt;br&gt; error LGHT0204: ICE38: Error 2235: &lt;Temp Dir&gt;/OU.AppFramework.Includes.msi, _Profile, UPDATE `Directory` SET
&gt; `_Profile`=0&lt;br&gt; error LGHT0204: ICE64: ICE Internal Error 1001. API
&gt; Returned: 1615.&lt;br&gt; error LGHT0204: ICE64: Error 2242:
&gt; OU.AppFramework.Includes.msi, _Profile, ALTER TABLE `Directory` ADD
&gt; `_Profile` SHORT TEMPORARY HOLD&lt;br&gt; error LGHT0204: ICE91: ICE
&gt; Internal Error 1001. API Returned: 1615.&lt;br&gt; error LGHT0204: ICE91:
&gt; Error 2242: OU.AppFramework.Includes.msi, _Profile, ALTER TABLE
&gt; `Directory` ADD `_Profile` SHORT TEMPORARY HOLD

Interestingly, this failure occurred before I left the office last night, and the solution compiled OK when I came in this morning. As it seems to centre on the temp directory where the MSI is build by WiX, could it be the build process locking the file?

Update 2:

And now we&#39;re back to over 600 errors, mostly repetition of this error:&lt;br&gt;

&gt; error LGHT0204: ICE30: ICE Internal Error 100. API Returned: 1615.&lt;br&gt;
&gt; error LGHT0204: ICE30: Error 2235: AppFramework.Includes.msi,
&gt; _ICE30SFN, SELECT `Directory_Parent`, `Directory`, `DefaultDir`, `_ICE30SFN`, `_ICE30LFN` FROM `Directory` WHERE
&gt; `Directory`.`Directory`=? AND `Directory_Parent`&lt;&gt;?

Update 3:

The problem still exists even after trying the suggestion by @limpan. There are a couple of warning given by light that are caused by the MSI output folder being locked when light tries to access the MSI:

&gt; Warning 549 The directory &#39;&lt;User Folder&gt;\AppData\Local\Temp\2opu3hxf&#39; is in use and cannot be deleted. light.exe


WiX ICE validation errors

I tried to use the codes below in Wix.

But when installing, the installer was freezing for like 3 minutes on status: Starting services, then I got this message &quot;Service Jobservice failed to start. Verify that you have sufficient privileges to start system services&quot;.
Is there any wrong in my codes? And can I ask the user to input the windows system user name and password during the installation to get the &quot;privileges&quot;? 

Thanks a lot!
           

        &lt;File Id=&#39;JobServiceEXE&#39; Name=&#39;JobService.exe&#39; DiskId=&#39;1&#39;
            Source=&#39;JobService.exe&#39; Vital=&#39;yes&#39; KeyPath=&#39;yes&#39;/&gt;         
        &lt;ServiceInstall Id=&quot;ServiceInstaller&quot; Type=&quot;ownProcess&quot; Vital=&quot;yes&quot;
            Name=&quot;JobService&quot; DisplayName=&quot;123 Co. JobService&quot;
            Description=&quot;Monitoring and management Jobs&quot; Start=&quot;auto&quot;
            Account=&quot;LocalSystem&quot; ErrorControl=&quot;ignore&quot; Interactive=&quot;no&quot; /&gt;
        &lt;ServiceControl Id=&quot;StartService&quot;  Stop=&quot;both&quot; Remove=&quot;uninstall&quot;
            Name=&quot;JobService&quot; Wait=&quot;yes&quot; /&gt;
    &lt;/Component&gt;


How to install and start a Windows Service using WiX

How do I create a shortcut on the desktop from a wix setup project?


Create shortcut to desktop using WiX

I&#39;ve used [ClickOnce][1] a lot over the years, but I have run up against a lot of its limitations. What alternatives are there for web deployment?

So far the only one I&#39;ve been able to turn up is [ClickThrough][2], which is part of [WiX][3] now on the back burner. Are there others that have had success?

  [1]: https://en.wikipedia.org/wiki/ClickOnce
  [2]: https://web.archive.org/web/20151226075116/http://blogs.msdn.com:80/b/robmen/archive/2005/11/08/490448.aspx
  [3]: https://en.wikipedia.org/wiki/WiX


What alternatives are there to ClickOnce?

I want to extract the MSI of an EXE setup to publish over a network.

For example, using Universal Extractor, but it doesn&#39;t work for Java Runtime Environment.

Extract MSI from EXE

In Visual Studio 2017&#39;s New Project dialog, there is no entry for Windows Installer XML (WiX). 

![enter image description here][1]

Is it possible to enable WiX projects in Visual Studio 2017?


  [1]: https://i.stack.imgur.com/lQZMG.png

How to Enable WiX Projects in Visual Studio 2017

I&#39;m creating an installer for a website that uses a custom event log source. I would like our WiX based installer to create that event log source during installation.

Does anyone know the best way to do this using the WiX framework.

How do you create an event log source using WiX

I have created a WiX Bootstrapper project. When the installation runs, it presents a license agreement.

I want to create a bootstrapper without this step as I don&#39;t want it to show any license agreement. Is it possible to do it? If yes, how?


How to create a bootstrapper application without a license agreement step

When I am trying to create the installer i am getting the following error:

The directory **`ProgramMenuDir`** is in the user profile but is not listed in the **`RemoveFile`** table. 

How do I resolve this issue? Below is the directory structure I am using:

    &lt;Directory Id=&quot;ProgramMenuFolder&quot; Name=&quot;Programs&quot;&gt;
      &lt;Directory Id=&quot;ProgramMenuDir&quot; Name=&quot;E&quot;&gt;
        &lt;Directory Id=&quot;Monarch&quot; Name=&quot;Monarch&quot;&gt;
          &lt;Component Id=&quot;Monarch&quot; Guid=&quot;*&quot;&gt;                       
            &lt;RemoveFolder Id=&#39;Monarch&#39; On=&#39;uninstall&#39; /&gt;
            &lt;RemoveFolder Id=&#39;ProgramMenuDir&#39; On=&#39;uninstall&#39; /&gt;
            &lt;RegistryValue Root=&#39;HKCU&#39; Key=&#39;Software\[Manufacturer]\[ProductName]&#39; 
                                       Type=&#39;string&#39; Value=&#39;&#39; KeyPath=&#39;yes&#39; /&gt;
          &lt;/Component&gt;
        &lt;/Directory&gt;
      &lt;/Directory&gt;
    &lt;/Directory&gt;

All Wix Solutions on Gang of Coders

Total of 37 Wix Solutions