Consider built-in PackageTargetFallback support about msbuildsdkextras HOT 6 CLOSED

I think we can close this as the 2.0 SDK seems to do this already.

from msbuildsdkextras.

I was thinking about that.... do you know if it's an explicit list that has to be or only the "highest," "most compatible" version that needs to be there?

Wondering what the best choice is for each .NET Standard version. Happy to add that in my lib, not sure what people will say for the main PR.

from msbuildsdkextras.

Some folks on the nuget team have been very negative toward use of this property. Others have expressed high caution, saying it doesn't really do what you think it's doing... so I would keep it out of your original PR to keep the uncontestable stuff more likely to get in.

from msbuildsdkextras.

As for the answers to your questions, I don't know.

from msbuildsdkextras.

Yeah, if I do this, I'd submit it as a separate PR to not mix purposes. I'm really not sure why this isn't already "in-box" though. Despite the desire to get people off of pcl profiles, all it does is cause developer pain until enough of the ecosystem has updated to netstandard :/

from msbuildsdkextras.

Yup. I think some nuget folks use it as a forcing function to get authors to update their packages to .netstandard. But I agree: it's mostly just pain, and if this alleviates the pain, but slows down migration slightly, IMO that's still a net win.

from msbuildsdkextras.