Documentation is what is found in the headers. You'll find those in the SDK\VS###\inc folder. > >All the WiX code uses those, so there are many examples.

In v4, the WiX Toolset MSBuild integration will be available via NuGet (as an SDK-style project) and the wix.exe is a dotnet tool will be available via NuGet (dotnet tool -i). We're also updating all of the projects to play better with NuGet so you can (for example) use .nupkgs in managed custom action projects and (if all goes well) reference ...

Feb 1, 2018 · NET.Build.Extensions\net461\lib\System.Xml.XPath.XDocument.dll;D:\Projects\Garnishment Manager\GarnishmentManager\Library\DelphiaLibrary.dll;C:\Program Files (x86)\WiX Toolset v3.11\SDK\Microsoft.Deployment.WindowsInstaller.dll;D:\Projects\Garnishment Manager\packages\Newtonsoft.Json.10.0.3\lib\net45\Newtonsoft.Json.dll;D:\Projects\Garnishment ...

I went with installing WiX Toolset through Chocolatey. Same with the Windows 10 SDK. Chocolatey allowed me to install WiX silently in a Docker image. choco install wixtoolset choco install windows-sdk-10.1 /Sverre tor. 4.

The closest thing to something being installed is you might be able to > take the dotnet-wix nuget package created from the Tools appveyor.cmd and > install it as a dotnet tool. You might be interested in this old thread - > http://lists.wixtoolset.org/pipermail/wix-devs-wixtoolset.org/2019-January/001203.html >.

You'd setup a build folder in the nuget package containing WixToolset.Dtf.MSBuild.props which initializes a Property named something like WixCATargetsPath to the path of wix.ca.targets. wix.ca.targets would be in the tools folder, and so would MakeSfxCA.exe.

However, when I looked into MSIX, it appears to no be fully mature and I plan to stay with MSI (just one example - MSIX is not natively supported on Windows). Any thoughts on whether MSI will be obsolete? If so, I don't think it would happen in the near future at all. Does WIX plan migration path to MSIX?

The MSI SDK is now part of the Windows SDK. WiX v2.0 supported I2 file sequences but that was dropped in WiX v3.0. We've recommended using the same version of WiX for servicing because otherwise we're guaranteeing cross-version patch compatibility and that's a high bar.

If your extension reports it can target VS2017 or newer (say, [10.0,)) then, yes, it must be built by the VS2017 SDK. So this goes for v1 and v2. VS2012 SDK through VS2015 SDK can produce v2s that can go on the Marketplace so long as they …

You can download Orca from https://www.technipages.com/download-orca-msi-editor On Mon, Apr 10, 2017 at 10:39 AM, Habib Salim <habib at hsalim.com> wrote: > Hi, > > I just tried a few versions of the Windows SDK - Win7/FW3.5, Win7/FW4, > Win8 > > One of them have MSI tools.