Feb 9, 2015 · WiX is a language (XML/XSD) that serves as a way of authoring (compiling) Windows Installer (.MSI) databases. WiX doesn't install anything, MSI does. I maintain an open source project called IsWiX. The concept is simple. IsWiX provides additional WiX project templates (scaffolding) and graphical designers to assist you in creating installer.

Jan 18, 2017 · If you install the MSI file producing a log then it may show what's going on: msiexec /I [path to msi file] /l*vx [path to text log file] It's possible that there is something in your setup that is causing this on that machine, especially if it performs another setup or a driver install (or something like that) that leaves the system in a state ...

Oct 23, 2017 · First concentrate on creating well working msi installer for ASP.NET application only - point 4 - and perhaps just use self hosting app. This would significantly simplify deployment as one of he prerequisites (.NET Core) does not have to be bootstrapped - …

Aug 26, 2014 · Beyond this, if the product has the same product code of the MSI, the installation offers the repair/change options: to disable them you have to play with the Property table of the Wix package, by introducing the ARP_ variables (you can disable repair, change and uninstall, but also setup manufacturer contacts and other properties).

I'm creating a program which is being installed by Wix, using VS 2010 and I've already got the product.wxs ready. In my wxs file, I've got directory definitions which looks like this: <SetDire...

Apr 4, 2013 · For example we have two products to install viz. Sample1.MSI and Sample2.MSI. We need to embed Sample2.MSI package into Sample1.MSI. If we install Sample1.MSI it should install both Sample1.MSI and Sample2.MSI and this should create two entries in Add or Remove programs (appwiz.cpl).

Mar 31, 2012 · I am using WiX 3.6 and VS2010. I have a 32-bit installation working and I'm trying to get a 64-bit installation working. I set the Platform to "x64" in the Configuration Properties. I set the Platf...

You can extract an embedded .msi from your bundle while it's running if you're using a custom bootstrapper application, then extract the contents of that .msi by using the WiX SDK. The short answer is that you can use the Unbinder class to extract the MSI files from your bundle:

MSI does not request admin rights until the InstallExecuteSequence. To get admin rights from the beginning you would have to use a bootstrapper, look at the Burn Engine provided with WIX. To get admin rights from the beginning you would have to use a bootstrapper, look at the Burn Engine provided with WIX.

If you are using MSBuild, SharpDevelop or Visual Studio (non-Express), you can use the WiX Bootstrapper project template. If you prefer to call the toolset command-line tools yourself, they are candle and light, just like for building MSI files. See the WiX 3.7 docs on "How To: Install the .NET Framework Using Burn".