-
Notifications
You must be signed in to change notification settings - Fork 428
Compatible versions of Visual Studio projects targeting netstandard nuget packages #241
Comments
VS 2015 had some minimal support for .NET Standard projects via the old PCL projects, however the recommended projects are base .NET Core tooling that ships only with VS2017 so yes in order to create .NET Standard libraries it would require VS2017. You will be able to consume one in earlier version of VS but not produce one. |
Thank you. So just to be sure I understand, using Visual Studio 2012 as an example, I can utilize a nuget package that only contains a netstandard library, I just can't create one without using Visual Studio 2017.
…Sent from my iPhone
On Mar 15, 2017, at 23:51, Wes Haggard ***@***.***> wrote:
Closed #241.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
For consuming the a nuget package that contains a netstandard library all you need is the updated nuget client. I believe the nuget team is still actively maintaining the nuget client down to VS2013. However you could always run the nuget restore from the command line with the latest nuget.exe if necessary as well. |
FWIW: The |
@emgarten can correct me if I'm wrong but I though the older nuget version also nows about netstandard. |
NuGet 2.12 has netstandard support. You can find it here: http://dist.nuget.org/ |
Ah, my mistake. https://docs.microsoft.com/en-us/nuget/release-notes/nuget-2.12 Thanks for clarifying! |
Is there any documentation on which previous versions of Visual Studio solutions/projects can utilize nuget packages targeting only netstandard? By adopting netstandard, are we also dropping support for any Visual Studio version prior to 2015?
The text was updated successfully, but these errors were encountered: