Created manifest for Dell Command Monitor 10.6.0

[prboyer]

• 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.0 schema?

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

---

Submission containins materials of a third party: Dell Inc.

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @prboyer,
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.

[Trenly]

This package has a dependency that .NET Framework 4.6.1 or later is installed.
It may also have a dependency to only be run on dell hardware, which I couldn't test on my VM

[prboyer]

@Trenly I believe both are true:

• This package has a dependency that .NET Framework 4.6.1 or later is installed.
• It has dependency to only be run on Dell hardware

Is there a way to specify either of these dependencies/requirements in the YAML manifest? I would imagine there has to be a way to link dependencies like .NET Framework 4.6.1.

[Trenly]

There are ways to mark the dependencies in the manifest. The 1.0.0 schema should be helpful for showing how to do this. I haven’t done it myself, but I believe it would be something like:

Dependencies:
  PackageDependencies:
  - PackageIdentifier: Microsoft.dotnet
     MinimumVersion: 4.6.1

However, the CLI currently doesn’t support automatic installation of dependencies; Its being tracked in microsoft/winget-cli#163 .

Custom hardware requirements are also not implemented yet, but are being tracked by #199504

Unfortunately, these block the PR from being validated until the CLI supports both dependencies and custom hardware

[ItzLevvie]