search

kbilsted / StatePrinter

Automating unit testing and ToString() coding
Apache License 2.0
93 stars 32 forks source link

Netstandard support #52

Open juanfranblanco opened 6 years ago

juanfranblanco commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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

kbilsted commented 5 years ago

a step in this direction has taken place now.

kbilsted commented 5 years ago

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

sebfrie commented 3 years ago

Is there still work going on regarding this issue?

kbilsted commented 3 years ago

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