Skip to content

[WiX 5] Migrate SDK from v3 to v5 #48699

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 26 commits into
base: main
Choose a base branch
from
Draft

[WiX 5] Migrate SDK from v3 to v5 #48699

wants to merge 26 commits into from

Conversation

joeloff
Copy link
Member

@joeloff joeloff commented Apr 24, 2025

Overview

This PR migrates the .NET SDK from WiX 3.14 to using 5.0.2. The package used is different from the public toolset and built from source.

Changes

  • Add separate SDK style projects for each installer: CLI, templates, and Visual Studio placeholder and standalone bundle.
  • Add .wixproj files as ProjectReferences to dotnet-sdk.proj and assign an Idle target. This allows the projects to participate in restore operations, but avoids being built as an actual reference. The projects depend on various values that are unavailable when project references are resolved.
  • Convert .wxl files to the v4 schema
  • Delete all the generate*.ps1 scripts that previously invoked Candle and Light. These tools no longer exist in v5.
  • Generate a PackageGroup for MSIs to chain into the SDK bundle. This avoids repeating the same authoring and simplifies adding additional MSI packages in the future (assuming they follow the same pattern).
  • Bundles will now match the target architecture. In v3, bundles were always 32-bit applications. This should be documented as a potential breaking change since detection logic will need to search under both registry views.

@joeloff joeloff changed the title [WiX 5] Migrate SDK from v3 to V5 [WiX 5] Migrate SDK from v3 to v5 May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant