Home: NuGet.Core for .NET Standard/.NET Core

[terrajobst]

What is the replacemet for NuGet.Core package on these platforms? It would be good to update the description.

Related: https://github.com/dotnet/standard/issues/652

[nkolev92]

There's no good documentation pointing to that.
The new packages are the actively updated ones on https://www.nuget.org/profiles/nuget.

We would need to build a new package just to update the description in this case.

//cc @rrelyea and @anangaur to help decide what the directions here would be.

[terrajobst]

Funny enough, the new location includes NuGet.Core 😆

Also, I believe you can edit the metadata of packages without uploading a new version.

[nkolev92]

Not since we've implemented Package Signing.
See https://github.com/NuGet/Home/wiki/Package-Immutability.

You can no longer make metadata updates without uploading a new version.

/cc @skofman1

[terrajobst]

Oh I see. I thought you still change the web site. My bad then. Well, I guess we need to figure out how to obsolete packages then because we'll have the same problem for ours.

[nkolev92]

Yeah, definitely.

We have a feature on the backburner, but personally I don't know when that would happen https://github.com/NuGet/Home/issues/2867

[anangaur]

We have a feature on the backburner, but personally I don't know when that would happen #2867

Soon 😄

[terrajobst]

13th of soon is my favorite ship date :-). Seriously, is this something you consider for an upcoming release? Is there a spec somewhere?

[anangaur]

@terrajobst We do plan to implement deprecate packages feature and will be scheduled by end of this quarter. I have an initial spec here that needs some revision that I intend to do in next couple of weeks.

[bdominguez]

Any news @anangaur ??

[anangaur]

@bdominguez about this issue or about Deprecate packages? Deprecate package spec is in progress and we plan to publish the spec for review in a week or two.

[bdominguez]

Sorry, I meant about this issue.

[nkolev92]

@bdominguez

The few core NuGet libraries are the following:

NuGet.Commands,
NuGet.Packaging,
NuGet.Protocol,
NuGet.PackageManagement

These have multiple other dependencies but those are lower on the dependency graph, so they'd be pulled in by the above.

Other than that, it's helpful to look at https://www.nuget.org/profiles/nuget, and just use the ones that are updated regularly.

[bdominguez]

https://www.nuget.org/packages/NuGet.PackageManagement/

Doesn't target .net standard I suppose because of:

https://www.nuget.org/packages/Microsoft.Web.Xdt/

Is there any solution?

[nkolev92]

No, PackageManagement is primarily packages.config, it's not used in the cross platform tools, so it was never made cross platform.

[bdominguez]

@nkolev92 but as I understand the only blocking issue that it's preventing from being cross platform it's that dependency I mentioned.

[nkolev92]

@bdominguez
Yes, probably, but we'd need to do some looking.

As I mentioned NuGet.PackageManagement primarily contains code used by VS/packages.config related code which is not cross plat by design.
There are some other classes which are unnecessary with PR, due to the fact that everything boils down to a restore.

The NuGet Client repo is primarily a tool, then library, so that just hasn't been a priority.

Why do you need it?
You can consider creating a fork.

[bdovaz]

Is there any reason it doesn't also target .NET Standard 2.0?

The problem now is that with 1.6 requires many many nuget package dependencies. In 2.0 we will reduce it drastically.

[nkolev92]

We're doing that in 5.0.
https://github.com/NuGet/NuGet.Client/pull/2118

[bdominguez]

Estimated ETA? Thanks.

[nkolev92]

5.0 will ship along side VS 2019.
I don't have exact dates yet, but it will be in the first half of 2019.
Preview packages with the NS2.0 change, might happen somewhere in ~February.

[oakio]

No, PackageManagement is primarily packages.config, it's not used in the cross platform tools, so it was never made cross platform.

@nkolev92 Is any official cross-platform replacement for NuGet.PackageManagement package?
For example, I need InstallPackageAsync method from this package.

[grahamehorner]

any updates; I'm looking at using NuGet as a plugin/module delivery for a cross platform microservice framework I have been developing; and would need NuGet.Core to support .net standard 1.6 or better or have the features that NuGet.Core allows in a cross platform package? any help or advice greatly received.

[nkolev92]

@grahamehorner Please refer to https://github.com/NuGet/Home/issues/7412#issuecomment-442646312.

The NuGet.Core package itself will not be updated.

[nkolev92]

Looping back here, the feature we discussed in https://github.com/NuGet/Home/issues/7412#issuecomment-433243759 is now shipped!

If you go to https://www.nuget.org/packages/NuGet.Core/, you will see that it's deprecated.

Furthermore we have improved the docs a tiny bit. https://docs.microsoft.com/en-us/nuget/reference/nuget-client-sdk