WiX: begin the extraction of the legacy SDK #461
+155
−36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces conditional support for including a legacy Windows SDK in the build and installer process. The main change is the addition of the
IncludeLegacySDK
property, which controls whether legacy SDK components are included. The build scripts, installer projects, and configuration files have been updated to selectively include legacy or experimental SDK files and components based on this property.Conditional legacy SDK support
IncludeLegacySDK
property toDirectory.Build.props
and passed it through build constants to enable conditional inclusion of legacy SDK components. [1] [2]installer.wixproj
andwindows.wixproj
to conditionally add references to legacy SDK project files and components whenIncludeLegacySDK
is set to true. [1] [2]installer.wxs
to select between legacy and shared MSI packages depending on the legacy SDK flag. [1] [2]Installer and component configuration changes
windows.wxs
to define SDK roots, directory structures, and component groups for legacy SDK files, ensuring only the relevant files are included based on the build configuration. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25]These changes make it possible to build and install either the legacy or experimental Windows SDK by simply setting the
IncludeLegacySDK
property, improving flexibility and easing the transition to the new SDK.