Submitting RoslynPad version 19.0.0

[aelij]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• 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).

[ghost]

Hello @aelij,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[ghost]

Hello @aelij,

The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

[Trenly]

@msftbot zip

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @aelij,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[aelij]

@Trenly the validation is failing because I've used schema version 1.4.0 (needed to support zip). Can this PR be merged now or do I need to wait for a non-preview release of winget that supports it?

[wingetbot]

/AzurePipelines run

[aelij]

@ItzLevvie I've updated the package to the latest release. Can this be merged now?

[ItzLevvie]

[Policy] Blocking-Issue

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Manual Validation ended with:

[stephengillie]

Hi @aelij,

This package displays the above message even with Microsoft.DotNet.AspNetCore.8 preinstalled. Can you help me to find the correct dependency?

[aelij]

@stephengillie the app needs a .NET SDK of any supported version. It should not be a dependency, as the users can choose the version according to their needs.

If you want to try out the app you can install Microsoft.DotNet.Sdk.8.

[stephengillie]

I'll consider this to be normal program operation. We're working on a kind of wildcard system for dependencies, which might allow any .NET SDK to be selected, and could be a better solution for this situation.

[wingetbot]

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