C#•11mo ago

✅ Non-nullable property netstandard2.0

Hello,
In new .NET versions there's the

required

required

keyword for this warning, but what's the best way to solve this if not possible?
Recently allowed a library to support older .NET versions, and I have no idea what's the preferred way to resolve this.

Sehra•2/9/25, 8:14 PM

try setting LangVersion to 11.0 or higher

CoreOP•2/9/25, 8:17 PM

it is set to latest

CoreOP•2/9/25, 8:17 PM

CoreOP•2/9/25, 8:20 PM

Oh it actually works

CoreOP•2/9/25, 8:20 PM

Great

CoreOP•2/9/25, 8:22 PM

It doesn't afterall

Sehra•2/9/25, 8:25 PM

it's just attributes, so could include them manually

TeBeCo•2/9/25, 8:37 PM

PolySharp

TeBeCo•2/9/25, 8:38 PM

i'm curious why you have 2 EOL TfM

TeBeCo•2/9/25, 8:38 PM

and 1 that is practicly never ever usse

TeBeCo•2/9/25, 8:38 PM

and 1 that is dying more than fast

CoreOP•2/9/25, 8:39 PM

you mean netstandard 2? Shouldk I completely ditch it?

TeBeCo•2/9/25, 8:39 PM

is it a nuget package publicly available on nuget.org ?

CoreOP•2/9/25, 8:39 PM

this one not, but the next one will be

TeBeCo•2/9/25, 8:39 PM

if that one is not ditch it

TeBeCo•2/9/25, 8:40 PM

do you have explict customer requirign net46 to net48 support ?

TeBeCo•2/9/25, 8:40 PM

or ultra weird thing ... like maybe Unity but i don't even know if unity properly support nuget packages

TeBeCo•2/9/25, 8:40 PM

netstandard2.1 is completly useless if YOU don't need it

TeBeCo•2/9/25, 8:41 PM

since your code also target ns2.0 i guess YOU don't need it

TeBeCo•2/9/25, 8:41 PM

net6.0 is dead

TeBeCo•2/9/25, 8:41 PM

net7.0 is dead

TeBeCo•2/9/25, 8:41 PM

this leaves you with net8.0 and net9.0

TeBeCo•2/9/25, 8:41 PM

add ns2.0 if you have consumer needing anything netfx or other non core target

TeBeCo•2/9/25, 8:42 PM

ns2.1 bring you IAsyncDisposable and IAsyncEnumerable

TeBeCo•2/9/25, 8:42 PM

but as opposed to "runtime target" ns2.x is more what do YOU need as a set of API this time

CoreOP•2/9/25, 8:43 PM

Got it, most open source propejcts support these, and that's why I was trying it out

TeBeCo•2/9/25, 8:44 PM

if you don't have a demand for it, don't overdo it

TeBeCo•2/9/25, 8:44 PM

a lot of open source project HAD that during the transition to core

TeBeCo•2/9/25, 8:44 PM

some kept it with no good reason

TeBeCo•2/9/25, 8:45 PM

some still have consumer on netfx or others and thus have good reason

TeBeCo•2/9/25, 8:45 PM

some keep it for explicitly bad reasonning

CoreOP•2/9/25, 8:51 PM

Is netstandard 2.1 only used by unity?

CoreOP•2/9/25, 8:52 PM

TeBeCo•2/9/25, 8:59 PM

that's not how it works for netstandard

TeBeCo•2/9/25, 8:59 PM

this image show what CAN run ns2.1

TeBeCo•2/9/25, 9:00 PM

if your code DO NOT NEED ns2.1 => DO NOT USE ns2.1

TeBeCo•2/9/25, 9:00 PM

ns2.x are like interfaces

TeBeCo•2/9/25, 9:00 PM

it let your own nuget code uses some apis

TeBeCo•2/9/25, 9:00 PM

and will garantee that the runtime it runs on will have these apis implemented

TeBeCo•2/9/25, 9:01 PM

meaning that if you don't need specific api, that are specific to ns2.1, then you shouldnt target ns2.1

TeBeCo•2/9/25, 9:01 PM

same for ns2.0

TeBeCo•2/9/25, 9:01 PM

now ... net5 net6 net9 .... are runtime

TeBeCo•2/9/25, 9:01 PM

you'd explicitly be targeting a runtime version, done

TeBeCo•2/9/25, 9:01 PM

that's it

TeBeCo•2/9/25, 9:05 PM

ns2.0 or ns2.1 was mostly only if you know already you'll have non-netcore consume part of these list

CoreOP•2/9/25, 9:10 PM

yeah I diteched it

CoreOP•2/9/25, 9:10 PM

Thanks for the details

TTeBeCo PolySharp

CoreOP•2/10/25, 1:14 PM

How does this work? I get that it will enable all the new syntaxes that are possible in newer .NET versions, like nullable types, required properties, etc.

But what happens after building the package, and

required

required

was used? Will it simply be omitted in the compiled executable?

Sehra•2/10/25, 1:20 PM

required is only an attribute