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.
Intent to drop .NET Core App 2.1 as target framework
See original GitHub issueRelated to #438, I intend to drop netcoreapp2.1 as a target framework. Note that the package still supports netstandard 1.4, which is the reason I’m going to drop the core app as a target. Somebody can correct me if I’m wrong here, but there’s no need to target netcoreappX when we’re already targeting netstandard, as the netstandard package will continue working in a .NET Core app without any changes. I think I was just a little confused about the new .NET versioning/framework naming scheme when it was added as a target.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (5 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
@nozzlegear why can’t the library simply target
netstandard? It should work in .NET Framework and DotNetcore. From my quick scanning of the code I do not see the issue with supporting onlynetstandard. Thoughts?Our 2.1 applications have some dependencies on some
netstandard1.xpackages. So it shouldn’t be a problem.Microsoft provides a
netstandardcompatibility table here: Interactive Table