State of NuGet Blog

[jcjiang]

Have thoughts after reading the State of NuGet blogpost? Share here.

[Rand-Random]

Just in case you missed the blog, like I did, here is the link
https://devblogs.microsoft.com/nuget/state-of-the-nuget-ecosystem/

[brettrowberry]

One thing I struggle with is that the .NET SDK isn’t a direct replacement for nuget.exe. I think it should be.

[brettrowberry]

Don’t remember. I think it was creating packages from multiple projects.

[Rand-Random]

@brettrowberry That is definitely one of our goals. What are the biggest areas that are missing parity today?

For me it is the inability to use commands without project/solution eg. add/init/install commands.

That‘s the main reason why I used nuget.exe for my reported issues here
#10579
#10593
#10618

I want to work directly with nuget packages and not with projects.

For one job neither dotnet nor nuget was enough and I had to use https://github.com/dotnet-outdated/dotnet-outdated

I needed a „dotnet restore“ for all packages with the PackageId „Foo.*“

[JonDouglas]

@brettrowberry This one? #3891

[JonDouglas]

@Rand-Random Although we've responded to a number of those issues already, you're basically asking to separate packages from projects/solution? Maybe a new discussion would help us discuss that further.

As for the dotnet-outdated project, what aspects of that tool would be beneficial if NuGet supported them in dotnet CLI or Visual Studio? Would love another issue or discussion talking about your ideas here. For example there is #4103 & various list commands to check deprecation/vulnerabilities.

[brettrowberry]

Here’s another #10398