Wixpack task updates#16043
Conversation
joeloff
left a comment
There was a problem hiding this comment.
LGTM. Is anyone using $(env.) or $(sys.)? I assume we can just add them later if it comes up.
Yeah, this case is interesting: What should
|
At first I considered moving preprocessor code to a different file. But, it later became intertwined with the task as it needs to call some of the methods, i.e. to ingest variables. |
So, this seems to be set by Wix toolset to the value of |
This addresses issues uncovered in dotnet/aspnetcore#62885
Most important change is additional support for collection of content that is applicable for installer scenario, based on preprocessor conditions. This ensures that we collect the correct files and properly evaluate all properties, define-constants and variables.
Changes
if,ifdef,ifndef,elseandelseifBinaryelements, used for custom action contentBindPathsandLocalizationFilesValidation:
Tested all current SDK installers and 3 of the ASP.NET installers that are building at the moment.
Notes for developers
To support
BindPathsandLocalizationFiles, via optional task parameters, add the following parameters to your task invocation: