Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Question: Should it be `NETCOREAPP5_0` or `NET5_0`?
See original GitHub issueWith the release of .NET 5 preview 3, the TFM has changed from netcoreapp5.0 to net5.0. However, the Define Constant for the TFM is still NETCOREAPP5_0 rather than NET5_0.
Is this intentional (e.g. for back-compat), something that hasn’t been done yet but is planned, or a bug because it should have been done as part of preview 3 and missed?
Sorry if this is the wrong repo, I wasn’t sure if this was an SDK thing or a compiler thing. I had a look in runtime, sdk and roslyn and couldn’t seem to find anything about this topic.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It will be
NET5_0, withNETCOREAPPstill defined for backwards compatibility. The spec for this is here: https://github.com/dotnet/designs/blob/master/accepted/2020/net5/net5.md#preprocessor-symbolsWe have a PR in progress for it here: https://github.com/dotnet/sdk/pull/11635
Looks like the change from
NETCOREAPP5_0toNET5_0happened in preview 7.