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.
.NET Standard Support Removed from Lamar 7 - Can I Add It Back?
See original GitHub issueWondering if there was a specific reason for removing .NET Standard 2.0 support from Lamar 7.
The commit that removed .NET Standard from everything was just removing it from the .csproj <TargetFrameworks> elements (basically).
I tried out adding .NET Standard 2.0 back into the Lamar source code where it was removed. Everything compiled and all the tests passed.
I’m looking for a version of Lamar that works with .NET Framework 4.7.2 (so .NET Standard 2.0) and Microsoft.Extensions.DependencyInjection 6.0. Weird combo I know. I can explain more if you’d like.
Would you accept a PR adding back in .NET Standard 2.0 and MS.E.DI 6.0 support? I can add in whatever kind of testing you like. Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (2 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
@twinter-patriot I just didn’t want to have to support the full .Net framework to be honest. And yes, I’ll take a PR. You’ll need the core Lamar.Testing library to also target .Net 4.7.2 whatever, and be running in the GH actions.
This is done.