[MANAGER] NuGet

[lk-code]

It would be great if WingetUI would also support the installation of packages via "dotnet tool". Tools can be loaded from NuGet via dotnet tool:

How to manage .NET tools dotnet tool install

There are already some very useful tools for dotnet tools and it would be great if you could manage them via WingetUI (search, installation and updates)

[marticliment]

Yes, this could maybe be a thing.

what kind of packages can you find on nuget/dotnet tool?

[Atrejoe]

As there are not many tool yet, you can easily find all using:

dotnet tool search \a --take 1000

Then add --skip 1000 a few times untill you are at the end.

Some popular tools are:

Package ID	Downloads
cake.tool	33.917.090
dotnet-reportgenerator-globaltool	22.004.778
gitversion.tool	21.664.578
dotnet-ef	19.287.400
dotnet-sonarscanner	12.469.937
dotnet-dump	12.410.746
amazon.lambda.tools	11.897.344
dotnet-gcdump	7.389.443
paket	5.758.002
swashbuckle.aspnetcore.cli	5.648.721

I produced a few myself, which are just handy cross-platform command-line tools.

My alpha examples (shameless lug):

• cs.changelog.console a changelog generator, based on Git repositories
• michaelchecksum.console a pun-based checksum calculator
• changedisplaysettings commandline tool to change display resolution (Windows only), simple wrapper on top of @lust4life 's work

[marticliment]

I will try to, i must check its licenses, but if they are compatible this might do its way into WingetUI

[NatanFreeman]

If NuGet/dotnet packages are planned on being supported, will package managers for programming languages like Cargo or NPM be considered as well?

[NatanFreeman]

Also, the name "WingetUI" doesn't make much sense anymore as the scope of the project has grown to include things like Scoop and Chocolatey as well. Will a rename be considered?

[marticliment]

If NuGet/dotnet packages are planned on being supported, will package managers for programming languages like Cargo or NPM be considered as well?

i am studying this, and they might, yes.

Also, the name "WingetUI" doesn't make much sense anymore as the scope of the project has grown to include things like Scoop and Chocolatey as well. Will a rename be considered?

I'm aware of this, and I am thinking on a rebrand

[ppvnf]

pip would be cool as well and it would make a lot o sense since this is a project made mostly with Python

[marticliment]

Pip has restrictions on their search command, (more or less the same thing as winget search * --source msstore), so it would need to be further studied

[BUGProtectionAssociation]

If NuGet/dotnet packages are planned on being supported, will package managers for programming languages like Cargo or NPM be considered as well?

i am studying this, and they might, yes.

Also, the name "WingetUI" doesn't make much sense anymore as the scope of the project has grown to include things like Scoop and Chocolatey as well. Will a rename be considered?

I'm aware of this, and I am thinking on a rebrand

I think this wingetui name can be kept. But it no longer means WinGet's GUI graphical frontend. Instead, the package getui on Windows

Yes， winget ui ---> win get ui --->win package get gui

[marticliment]

win get ui

Yes, I like this approach!

[ppvnf]

WinPkgUI my suggestion

[marticliment]

Hello,

I have posted a discussion about rebranding WingetUI. Please share your thoughts here: https://github.com/marticliment/WingetUI/discussions/1561

[glen-84]

The initial comment is about tools, which I think are now supported?

Has this issue been repurposed for NuGet packages in general?

[marticliment]

Yep, the issue has been repurposed