NuGet Package Manager for VS 2012 does not support .NETStandard

[drieseng]

Version 2.8.60318.667 of the NuGet Package Manager - which is the latest version available for Visual Studio 2012 - does not support packages that defines dependencies for .NETStandard.

When - for example - a given package defines dependencies for both UAP10.0 and .NETStandard 1.3, then the following is reported:

'package name' already defines a dependency for 'dependency name'

I'm well aware that Visual Studio 2012 is pretty dated, but I lead an OSS project (SSH.NET) for which we want to support a broad set of target frameworks. This issue prevents us from having a single package for all our supported target frameworks.

An example of a .nuspec that exposes this issue is available here.

Let me know if you want me to upload a .nupkg that allows you to reproduce the error.

[rrelyea]

We shipped a version of 2.12 for VS2013 with NetStandard support on June 27th.
We wanted to ship one for VS2012 as well, however we ran into some problems. You are the first person to notice.

Putting into our current milestone to help us resolve the plan.

[drieseng]

Another option would be to release SL4, WP7 (...) framework targeting packs for VS2013 and/or VS2015 :-)

@rrelyea, there are some old milestones that need to be closed https://github.com/NuGet/Home/milestones. Such as 2.12, which is 100% done but still opened.

[drieseng]

Is this issue indeed scheduled to be fixed in 3.5 RTM (and 2.13) ?
I'm getting reports by users of SSH.NET almost daily.

[kl7323]

I'm one of the users still using VS2012, yes AT&T is still using it as a standard. I really need to SFTP files for a deadline fast approaching.

[drieseng]

@kl7323: as workaround, you can download the nuget package from nuget.org, extract it and pick the assembly that you need.

[niemyjski]

This has been months since this was updated. Please release a 2012 nuget client that supports packages that contain .net standard. This is insane you are sitting on this this long when customers and end users now cannot use packages like JSON.NET

Still can't install on Visual Studio 2012! It kinda breaks the idea of nuget being the preferred deployment model for VS...

[ludzzz]

Same issue here, need to install protobuf-net.
Is there any update on this topic, or is it dead?
Thanks