Add: WiX Toolset

[FernandoNunes]

• Have you signed the Contributor License Agreement?
• [ x ] Have you checked that there aren't other open pull requests for the same manifest update/change?
• [ x ] Have you validated your manifest locally with winget validate --manifest <path>?
• [ x ] Have you tested your manifest locally with winget install --manifest <path>?
• [ x ] Does your manifest conform to the 1.2 schema?

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @FernandoNunes,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[wingetbot]

/AzurePipelines run

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @FernandoNunes,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[wingetbot]

/AzurePipelines run

[ghost]

Hello @FernandoNunes,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @FernandoNunes,

During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

Template: msftbot/validationError/installation/unattended

[FernandoNunes]

@stephengillie / @ryfu-msft / @mtodd I can't seem to get this installer to work on the Installer-Validation step, but all the various manifests configs I've tried they all "Work on my machine ™".
Are you guys able to help ?

Best regards,
Fernando Nunes

[Trenly]

• See Add WiXToolset 3.11.2 #895
• See NETFoundation.WiXToolsetv3 version 3.11.2.4516 #65900
• See NETFoundation.WiXToolset version 3.11.2 #58825
• See NETFoundation.WixToolset version 3.11.2 #25268
• See WiXToolset.WiXToolset version 3.11.2.4516 #23647

This has a dependency, which is why it is failing.

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

@msftbot dependencies

Close with reason: See above;