Created new Standard2.1 project and pulled in client from .NET 4.0 project for full features. #70
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…oject for full features.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had issue using this library from a .NET standard 2.1 library. Got some weird errors any time I tried to assign or access the parity properties when using RTU comms.
I created a new .NET Standard project, but based off the .NET 4.0 project instead of the .NET 5.0 project. This enabled most of the functionality I expected.
Note: I have not fully tested or vetted every possibility here. It looks like everything dependency wise lines up though. Since I have a real project moving forward with this fork, I will advise if I run into any issues, and hopefully fix them. Just thought this might be useful to others with the same roadblock.