-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: .NETStandard 2.0 support #2
Comments
Greetings, There shouldn't be any hard rule for why not supporting NETStandard 2.0, but it require some code changes since some language features are not supported in NETStandard 2.0. |
NETStandard 2.0 would allow to use the package also in full framework. Therefore if there's no hard dependency on Core, NETStandard 2.0 would be preferable. |
@BrightLight, yeah, we should be able to support |
Hey Moaid, I was just a bit interested in how to add .NET Standard 2.0 support and did it in the following branch: Just letting you know in case you want to take inspiration from it, however I am pretty sure its not a complete or good version - Looking at you DumpColor.cs But yeah, if you already have it all solved you can just ignore this. |
Hi @Hejle, thanks for this! |
Looking forward to see the adjustments! |
Hi @Hejle, I'm almost done. I did some modifications, but the result was inspired by your branch. |
@sadedil, @BrightLight, the work on this feature is done, and it should be part of the next release, which is due this month. Thank you for suggesting it :) @Hejle, the following is my branch. If you are interested in contribution (commit) credits, please say so and we will figure out a way. I'm planning to merge this branch into master during the weekend, but I can delay it if you need more time :) |
That sounds great @MoaidHathot. |
@BrightLight, @sadedil, @Hejle, the PR was merged into Main. I'll release the new version before end of month. |
@MoaidHathot, @Hejle thank you both. |
@sadedil, @BrightLight this has been released in version v0.6.0 |
Greetings,
Is there any hard rule to keep .NET dependencies >= .NETStandard,Version=2.1.
Can this support Version=2.0 too?
The text was updated successfully, but these errors were encountered: