Using Winget!

[Bjego]

Hey guys,

choco has been replaced by winget in the last few years. Could you provide an installation via winget as well?

Best regards

[MrHinsh]

We have tried!

microsoft/winget-pkgs#106774

"New applications which depend on .NET are being kept in a waiting list for dependency support, using the Dependencies label"

Our PR is blocked as we depend on .NET and Winget will not approve packages that have dependencies.

I think this is stupid and invalidates most small development tools. My conclusion is that Winget is primarily for commercial tools...

[Bjego]

Interesting - did you try to migrate to a current .net version (6,7,8) and then build & deploy it as standalone app?
Maybe then you can pass - Microsofts dependency check. And creating e.g. a docker container would be easier then as well. And from a developers perspective - you could use newer features and development technologies - then with .netstandart2.0.

I think the only trade off would be that people, who are using your nuget with full legacy .net framework , won't be able to update to the latest versions of your package. But from my point of view this is a reasonable tradeoff in 2023.

[MrHinsh]

1. No version of .NET is pre-installed on the target machines. All dependencies MUST be installed by the "installer"... since we are portable, there is no support.
2. We depend on "Microsoft.TeamFoundationServer.ExtendedClient", which ONLY works with FullFramework and does not support the current .net version.

All code that can be converted to the current .net version is currently on 8.0.

[MrHinsh]

The block for packages with dependencies has been lifted. You can now install with Winget.

We are testing the continuous delivery pipeline as we work: microsoft/winget-pkgs#122213

[MrHinsh]

You can now use winget install nkdAgility.AzureDevOpsMigrationTools to install the tools and keep them up to date.