Add WiXToolset 3.11.2

[chausner]

Note: WiX Toolset requires the .NET Framework 3.5 Windows feature to be enabled.

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

This submission has moved to manual review.

[TheQuazman]

Thanks for adding this, I was about to, but figured I should check the pull requests first.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

This submission has moved to manual review.

[ghost]

chausner The package manager bot determined there was an issue with installing the application correctly. Please check the application installs correctly. Once repaired, please push an update to your pull request.

[KevinLaMS]

when trying to install it showed an error, and shows UI.

[ghost]

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

[KevinLaMS]

Looks like there is a dependency that is missing.

[ghost]

chausner The package manager bot determined there was an issue with installing the application correctly. Please check the application installs correctly. Once repaired, please push an update to your pull request.

[KevinLaMS]

microsoft/winget-cli#182

[denelon]

This PR is a bit old 😄

I'm not sure if we need support for dependencies and/or standalone .exe applications for this to work.

In either case, the manifest needs to be updated to the current schema.

[chausner]

I'm not sure if we need support for dependencies and/or standalone .exe applications for this to work.

I would say this is a very special case since the external dependency (.NET Framework 3.5) is not a regular program/package but has to be enabled as a Windows feature.

[denelon]

@chausner we added support for Windows Features as a possible type of dependency in the v1.0 schema. We're still looking into the implications of making Windows Features as dependencies since it may require a reboot. I've seen one suggestion where they are created as "packages" so the package level dependency could be used. More analysis is required to understand edge cases and the best UX.

[KevinLaMS]

Clearing assignees until unblocked.

[Trenly]

I'm going to close this PR because it is so old and doesn't conform to any of the current schemas. Additionally, the base branch is (at the time of writing) 84,000 commits behind master and it would be better to create new manifests rather than rebasing or merging in master. I will leave #96043 open to track the progress against WiXToolset, as it is based on the latest updates to the manifest schema and is a newer branch from master. Thank you for your PR!

Close with reason: See above;