You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all package assembly have a NET_STANDARD_2_0 definition , which let unity reference them only when API compatibility level set to .NET Standard 2.0.
But .NET 4.x api level was compatible with .NET Standard 2.0, means if an assembly working under .NET Standard 2.0, it also working under .NET 4.x.
So there's no reason to limit packages to .NET Standard 2.0.
If you have some other thinking, please let me know, thanks.
The text was updated successfully, but these errors were encountered:
Currently all package assembly have a
NET_STANDARD_2_0
definition , which let unity reference them only whenAPI compatibility level
set to.NET Standard 2.0
.But
.NET 4.x
api level was compatible with.NET Standard 2.0
, means if an assembly working under.NET Standard 2.0
, it also working under.NET 4.x
.So there's no reason to limit packages to
.NET Standard 2.0
.If you have some other thinking, please let me know, thanks.
The text was updated successfully, but these errors were encountered: