Development in the blockchain space by the big industrial players is moving at a blazing pace and ARK continues to evolve and expand along side them by following the best development practices and providing the latest client APIs for integration into any existing blockchain system.
ARK-NET client API now supports custom build configurations for .NET Standard 2.0 and other .NET platforms, along with additional new functionality and improvements as listed below.
So, What Has Changed in ARKNET?
- Builds were added for multiple framework support.
- Asyncronous implementation of all client API calls.
- Added generic request structure for easier querying.
- Autoloader configuration from peers implementation.
- NuGet package creation for frameworks.
- Sending transactions to multiple peers for faster confirmations.
- Full unit test implementation of ARK-NET. That way we can grow with stability, and without fear of breaking any legacy code.
- Wait, did we mention full unit test implementation?
- Improved peer filtering and selection, based on quality filters.
- Core services implementation refactored.
- and much much more…
Github release page: https://github.com/kristjank/ark-net/releases/tag/v0.8.0
The code has been restructured, cleaned, and reorganized, so it should be easier on the eyes for new developers to get in and start using ARK-NET API.
What is .NET Standard
For the impatient: TL;DR
.NET Standard solves the code sharing problem for .NET developers across all platforms by bringing all the APIs that you expect and love across the environments that you need: desktop applications, mobile apps & games, and cloud services.
I want more info
- .NET Standard is a set of APIs that all .NET platforms have to implement. This unifies the .NET platforms and prevents future fragmentation.
- .NET Standard 2.0 will be implemented by .NET Framework, .NET Core, and Xamarin. For .NET Core, this will add many of the existing APIs that have been requested.
- .NET Standard 2.0 includes a compatibility shim for .NET Framework binaries, significantly increasing the set of libraries that you can reference from your .NET Standard libraries.
- .NET Standard will replace Portable Class Libraries (PCLs) as the tooling story for building multi-platform .NET libraries.
You can see the .NET Standard API definition in the dotnet/standard repo on GitHub.
Found an Issue?
Submit an issue report at : https://github.com/kristjank/ark-net/issues
Want to Contribute?
Join ARK Slack :
https://ark.io/slack/ ( #net_development channel)
Join ARK Gitter and talk with other developers :
https://gitter.im/ark-developers/Lobby
Special thanks to all of the community developers who helped with this great update — especially @sharkdev-j and @dnovacik and @kristjank (delegate Chris).
