AntonyCourtney.Tad version 0.12.0

[dpprdan]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[microsoft-github-policy-service]

Hello @dpprdan,

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).

[microsoft-github-policy-service]

dpprdan,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Template: msftbot/requiresApproval/moderator

[dpprdan]

@Trenly: wingetcreate apparently did not detect that the architecture is x64 not x86 (again, as you corrected the PR for the last version). Can you tell if this due to some misconfiguration in the Tad installer or a bug in wingetcreate that should be filed there?

Maybe related to microsoft/winget-create#329?

[Trenly]

@Trenly: wingetcreate apparently did not detect that the architecture is x64 not x86 (again, as you corrected the PR for the last version). Can you tell if this due to some misconfiguration in the Tad installer or a bug in wingetcreate that should be filed there?

Maybe related to microsoft/winget-create#329?

Wingetcreate looks at the installer's architecture to try and determine which it is. In this case, the installer is compiled for x86, even though the application inside will only run on x64

• wingetcreate looks for installer architecture instead of application architecture winget-create#198

There are a few ways to work around this.

1. Manually update after manifest creation
2. The publisher can update the installer URL to include _x64
3. You can use the architecture override syntax

[microsoft-github-policy-service]

Hello dpprdan,
Validation has completed.

Template: msftbot/validationCompleted

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.