@Jim8y
should we change the version number? If so to what? 0.3.0? or 1.0.0?

Let's use 0.0.3, let erik to decide when to use 1.0.0

@shargon

I think that we should use compiler directives, seems that there are a lot of reflection, it will be slower and harder to maintain.

@shargon this is the easiest way of doing it, without rewriting a lot of code. Reflection is fast now a days. Just think about all System Attributes in asp.net core and other libraries. They all use reflection for getting attributes

@shargon this is the easiest way of doing it, without rewriting a lot of code. Reflection is fast now a days. Just think about all System Attributes in asp.net core and other libraries. They all use reflection for getting attributes

Maybe we should wait for .net standard 3, why we need it right now?

neo-project/neo#3044 (comment)

netstandard2.1 is the last version ever; says microsoft.

netstandard2.1 is the last version ever; says microsoft.

Then this seems like it will not be maintained.

You have to understand what netstandard is

.NET Standard allows libraries to build against the agreed
on set of common APIs, ensuring they can be used in any 
.NET application—mobile, desktop, IoT, web, or anywhere you write .NET code.

https://dotnet.microsoft.com/en-us/platform/dotnet-standard#:~:text=NET%20implementations.-,.,NET%20code.

So they would wait for the OS to have some common APIs before they update dotnet standard. But there will still be support and bug fixes

My goal in the future is to get neo-core to convert, and have the blockchain run on a phone. Like a lite node. Plus help with developers want to run core or vm on phones or other platforms.

My goal in the future is to get neo-core to convert, and have the blockchain run on a phone. Like a lite node. Plus help with developers want to run core or vm on phones or other platforms.

☝️ this would be AWESOME. ❤️

@cschuchardt88 please, could you update the PR?

@shargon all done

Pull Request Test Coverage Report for Build 7463345327

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.1%) to 81.114%

Totals
Change from base Build 7457521814:	0.1%
Covered Lines:	2059
Relevant Lines:	2474

💛 - Coveralls

Nvm