MCWrapper 2.0.3-beta

• .NETCoreApp 3.0

  • Microsoft.Extensions.Configuration.Json (>= 3.0.0-preview6.19304.6)
  • Microsoft.Extensions.DependencyInjection (>= 3.0.0-preview6.19304.6)
  • Microsoft.Extensions.Http.Polly (>= 3.0.0-preview6.19304.6)
  • Microsoft.Extensions.Options (>= 3.0.0-preview6.19304.6)
  • Microsoft.Extensions.Options.ConfigurationExtensions (>= 3.0.0-preview6.19304.6)
  • Newtonsoft.Json (>= 12.0.2)

We implemented the Typed HTTP Client pattern incorrectly in previous versions of MCWrapper, this is fixed in 2.0.3-beta.
For RPC clients inject the interface instead of the concrete class now.
For example, instead of injecting BlockchainRPCClient, instead inject IBlockchainRPC;
The MCWrapper Unit Tests hosted on our GitHub repo have been updated to reflect the changes present in this release.
Fixed code comments to manifest through the interfaces instead of the concrete implementations.
Fixed and marked the Optional paramters for all RPC clients and CLI clients.

Pro Tip: Easiest method to configured MCWrapper with MultiChain node settings is to place the values as environment variables either in Visual Studio or your local operating system. When placed as environment variables a consumer may use the parameterless AddMultiChainCoreServices() method and the values will be detected when they become necessary during runtime.

This should be close the last beta release before a stable MCWrapper version 2 is released. At this time we will put more effort into our GitHub and Project sites to build up our documentation and tutorials.

Misc. Bug fixes;
Reduction in code comment duplication;
All RPC clients now inherit from RPCClient class to expose the TransactAsync method instead of hosting it locally within each RPC client as private properties and methods.

Modified WalletRPCExtensions to extend the IWalletRPC interface instead of the WalletRPCClient implementation;