Runtime: System.Drawing.Common lower .netstandard version?

[MattSFT]

Is it possible to downgrade the .netstandard requirement for https://www.nuget.org/packages/System.Drawing.Common?

I don't know enough about the specifics of this library so not sure it is possible, but I would like to use it in a project targeting .netstandard 1.3.

[karelz]

@safern I assume there is a reason we don't target lower .NET Standard. Can you please comment?

[safern]

@safern I assume there is a reason we don't target lower .NET Standard.

This is something no-one has ever asked before. When this library was ported back was on the 2.1 time-frame and since it is part of the Compatibility Package, that is the reason why it supports .NET Standard2.0, because that is the minimum the Compatibility Package should support. However, I've never tried to add support for an lower .netstandard and I don't know if all the APIs we use are available then.

However, this would force us to add a .netcore50 implementation for it, since the way this API is designed, it should have a runtime specific implementation, since we can't run in UAP (due to UWP restrictions and limitations).

[MattSFT]

Does that mean we can't do this?

I'm using this library currently by the way https://www.nuget.org/packages/CoreCompat.System.Drawing/ but would like to use an official MS published one

[safern]

Does that mean we can't do this?

It doesn't mean we can't do this, we might be able to get away on doing it, however it might take more work than we would expect and complicate that package even more and I know that is not our priority now, so I can't promise it would be done on a close time frame unless we get someone from the community to contribute and do it. @ericstj do you have any strong opinion on this? I would push back unless there is a very strong reason to do it... but other experts on packaging and framework support might contradict me because I might not be thinking of something else.

Is there any reason why you can't move to .netstandard2.0?

[MattSFT]

My project builds out a nuget that is used in a few older systems. Many of which I don't have control over and one of those refuses to upgrade beyond .netframework 4.6.

No technical limitations. I'll continue using the compat library until either my consumer upgrades or you folks downgrade.

[carlossanlop]

@safern I'll move this issue to the corefx repo + area-infrastructure

[carlossanlop]

@safern moved for easier tracking.

[jkotas]

We do not plan to back port any libraries to netstandard1.x. We recommend everybody to upgrade to netstandard2.0.