.NET Standard 2.0 support or Support .NET Maui at least

[logikonline]

I am quite surprised you guys didn't offer an RPC Client for use with .NET Standard 2.0. It really limits our options for rapid development. I want to use Xamarin Forms to build a few solutions using NEO, but I am struggling to use the RPC Client libraries.

[logikonline]

Gentlemen, at the very least, make a version one can include in .NET Maui.

I do not prefer this since Microsoft has a habit of taking a few years before control platforms provide the same suite of offerings as the predecessor, but at least we can start crafting solutions today. We cannot have the following in the assembly reference, though:

"NETSDK1082 There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'iossimulator-x64'."

[gsmachado]

so... maybe @devhawk could enlighten us here?

I'm not so into this topic (C# dependencies and stuff), but it seems @logikonline has a good use case to request for this...

[erikzhang]

Does MAUI not support net6.0?

[logikonline]

Does MAUI not support net6.0?

I actually worked offline with devhawk and he removed the code in a off branch which violated .NET Maui. Maui does support 6.0 but not Microsoft.AspNetCore.App which NEO needs for P2P - although this isn't needed for RPC Client functionality.

[devhawk]

Neo.dll drags along lots of dependencies that are only needed for running a full node. I helped @logikonline produce a custom neo.dll that removes the ASP.NET dependency so that can be used in .NET MAUI. But that custom assembly is still dragging in other dependencies like Akka.net that aren't needed in client scenarios.

Maybe it's time to revisit neo-project/neo#1865? That would address this issue (aka #749) as well as neo-project/neo#2678.