-
Notifications
You must be signed in to change notification settings - Fork 30
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
Netstandard support #52
Comments
As long as we can do it without cluttering the code with a lot of |
The thought was to target multiple frameworks using "TargetFrameworks" Also in that scenario it needs a property like this: |
Sorry I forgot about this issue. We need to analyse whether core has the same introspection capabilities and run time code generation. |
a step in this direction has taken place now. |
the .net version has been liftet to 4.6.1. so multiple frameworks should be easier supported now. Up for the task @juanfranblanco ? |
Is there still work going on regarding this issue? |
@sebfrie the features reading the registry cannot be ported to standard, perhaps someone can multitarget framework and core |
Will it be possible to create a new package targetting netstandard?
I have created a temporary package / project file and nuget targetting netstandard 2.0. Probably best to have a single project file multi targetting 3.5 and netstandard (Netstandard 1.0 might be possible).
https://github.com/Nethereum/StatePrinter/blob/master/StatePrinter/StatePrinter.NetStandard.Temp.csproj
Many thanks!
The text was updated successfully, but these errors were encountered: