As a Setup developer I can acquire extensions for use by a command-line build.
As a WiX extension developer I only have to publish my extension via NuGet and Setup developers can access it via the command-line build and MSBuild/NuGet project-based build.
Add a new command to
wix.exe to download and extract extensions from NuGet packages into an "extension cache" for easy reference by the
build command. This design is inspired by the
dotnet tool command which manages local and global .NET Core tools.
extension command will have three sub-commands:
add- adds the extension to the local or global cache. The NuGet package id must be provided and a specific version can be requested by appending slash and version to the package id. Otherwise, the latest package is added to the cache.
remove- removes an extension from the local or global cache. The NuGet package id must be provided and a specific version can be requested by appending slash and version to the package id. Otherwise, all versions of the package id are removed from the cache.
list- lists the extensions in the local or global cache.
Each sub-command accepts a
-g switch to use to the global cache instead of the local cache.
The extensions NuGet packages are extracted to a
.wix\extensions\[packageId]\[packageVersion] cache folder.
For local packages, the root cache folder is the current directory when the
wix.exe extension command is executed. Care must be taken by the Setup developer to set the current directory correctly when adding extensions and building using them.
For global packages, the root cache folder defaults to the user's home folder (
%USERPROFILE%). The global cache root folder can be overridden using the
WIX_EXTENSION environment variable.
Extensions in the cache can be referenced by their package id to get the latest version, for example:
wix extension add WixToolset.Util.wixext wix build -ext WixToolset.Util.wixext source.wxs
Note that the local cache is always checked before the global cache.
A specific version of an extension may also be referenced by appending the extensions' package id with slash and version, for example:
wix extension add WixToolset.Util.wixext/4.0.3 wix build -ext WixToolset.Util.wixext/4.0.3 source.wxs
Finally, extensions can always be referenced using a full path and will bypass the cache look-up, for example:
wix build -ext C:\ext\WixToolset.Util.wixext.dll source.wxs
Should MSBuild/dotnet build use the extension cache or only depend on project's package references being restored during the build?
Answer: No. Let the extension cache only be used by the command-line and the NuGet package cache used for MSBuild/dotnet build. This does mean the extensions shared between command-line builds and project based builds are cached twice but a) we don't expect devs to generally use both command-line and project based options and b) extensions are small.
Should we make the
.wixext optional when referencing via the
Answer: No. It is inconsistent as ".wixext" will be required to find the package in a NuGet feed.
What about a
wix extension restore command to bring down all the required extensions?
Answer: If the
extension command kept a log of extensions added to the local or global cache, it would be possible to have a sub-command like
restore re-download the extensions missing from the cache. This sort of restore functionality is not planned in the first version.
What about using a
--version switch for the
remove sub-commands instead of the "slash version" syntax?
Answer: While using a
--version switch would be more consistent with
dotnet tool behavior, the
build -ext switch needs a concise way to specify the extension package id and version. The "slash version" syntax is borrowed from the MSBuild SDK-style reference syntax.