Skip to content
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

Open
juanfranblanco opened this issue May 1, 2018 · 7 comments
Open

Netstandard support #52

juanfranblanco opened this issue May 1, 2018 · 7 comments
Assignees

Comments

@juanfranblanco
Copy link

juanfranblanco commented May 1, 2018

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!

@kbilsted
Copy link
Owner

kbilsted commented May 7, 2018

As long as we can do it without cluttering the code with a lot of #if and the like I see no problem with it.
Not sure what you suggest be the best way to maintain such a configuration. Also I haven't analyzed if all the reflection and run-time code generation is possible in .net standard

@juanfranblanco
Copy link
Author

The thought was to target multiple frameworks using "TargetFrameworks" "net351;netstandard20" if you want to keep targetting net35 friendly.

Also in that scenario it needs a property like this:
https://github.com/Nethereum/Nethereum/blob/master/buildConf/net35.props#L2-L4

@kbilsted
Copy link
Owner

Sorry I forgot about this issue. We need to analyse whether core has the same introspection capabilities and run time code generation.

@kbilsted
Copy link
Owner

a step in this direction has taken place now.

@kbilsted
Copy link
Owner

kbilsted commented Jun 3, 2019

the .net version has been liftet to 4.6.1. so multiple frameworks should be easier supported now. Up for the task @juanfranblanco ?

@sebfrie
Copy link

sebfrie commented Oct 20, 2020

Is there still work going on regarding this issue?

@kbilsted
Copy link
Owner

@sebfrie the features reading the registry cannot be ported to standard, perhaps someone can multitarget framework and core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants