MCWrapper.RPC 6.0.0

• .NETCoreApp 2.1

  • MCWrapper.Data.Models (>= 2.1.5)
  • MCWrapper.Ledger.Actions (>= 1.0.2)
  • MCWrapper.Ledger.Entities (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 2.1.0)
  • Microsoft.Extensions.DependencyInjection (>= 2.1.0)
  • Microsoft.Extensions.Http.Polly (>= 2.1.0)
  • Microsoft.Extensions.Options (>= 2.1.0)
  • Microsoft.Extensions.Options.ConfigurationExtensions (>= 2.1.0)
  • Newtonsoft.Json (>= 12.0.3)

• .NETCoreApp 2.2

  • MCWrapper.Data.Models (>= 2.1.5)
  • MCWrapper.Ledger.Actions (>= 1.0.2)
  • MCWrapper.Ledger.Entities (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 2.2.0)
  • Microsoft.Extensions.DependencyInjection (>= 2.2.0)
  • Microsoft.Extensions.Http.Polly (>= 2.2.0)
  • Microsoft.Extensions.Options (>= 2.2.0)
  • Microsoft.Extensions.Options.ConfigurationExtensions (>= 2.2.0)
  • Newtonsoft.Json (>= 12.0.3)

• .NETCoreApp 3.1

  • MCWrapper.Data.Models (>= 2.1.5)
  • MCWrapper.Ledger.Actions (>= 1.0.2)
  • MCWrapper.Ledger.Entities (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 3.1.0)
  • Microsoft.Extensions.DependencyInjection (>= 3.1.0)
  • Microsoft.Extensions.Http.Polly (>= 3.1.0)
  • Microsoft.Extensions.Options (>= 3.1.0)
  • Microsoft.Extensions.Options.ConfigurationExtensions (>= 3.1.0)
  • Newtonsoft.Json (>= 12.0.3)

• .NETStandard 2.1

  • MCWrapper.Data.Models (>= 2.1.5)
  • MCWrapper.Ledger.Actions (>= 1.0.2)
  • MCWrapper.Ledger.Entities (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 2.2.0)
  • Microsoft.Extensions.DependencyInjection (>= 2.2.0)
  • Microsoft.Extensions.Http.Polly (>= 2.2.0)
  • Microsoft.Extensions.Options (>= 2.2.0)
  • Microsoft.Extensions.Options.ConfigurationExtensions (>= 2.2.0)
  • Newtonsoft.Json (>= 12.0.3)

The following IMultiChainRpcWallet interface methods have had their return types changed to RpcResponse<string> from RpcResponse<object>;
GrantAsync
GrantFromAsync
GrantWithDataAsync
GrantWithDataFromAsync

IssueAsync and IssueFromAsync methods are now expressed with generic and strongly (AssetEntity class) typed object parameters. Consumers may now also simply pass a string type unique name to these methods, versus using either object argument type option.

IssueAsync and IssueFromAsync methods with a 'customFields' parameter are now have the parameter expressed as a Dictionary<string, string> instead of a generic object. Hopefully, this will make using the API a bit more explicit and easier to pass multiple fields.

IssueMoreAsync and IssueMoreFromAsync with a 'customFields' parameter are now have the parameter expressed as a Dictionary<string, string> instead of a generic object. Hopefully, this will make using the API a bit more explicit and easier to pass multiple fields.

Change to MultiChainRpcClient - Now only requires the base data type, to be wrapped by the RpcResponse, to be passed into the method. We now simply infer the RpcResponse type during Json deserialization. Probably a micro optimization but puts our RPC clients more in sync with how our CLI client library is constructed, more consistent code-base between our different libraries.

A new Target Framework has been added, netstandard2.1.

Prior to the release we are targeting:
netcoreapp3.0;netcoreapp2.2;netcoreapp2.1

Post release we will target:
netcoreapp3.1;netcoreapp2.2;netcoreapp2.1;netstandard2.1

We added several more data models to make our return types more strongly typed.

Many methods return generic object types, they now return more specific accurate data model types or base types (string, bool, int, etc...).

Please view all supported MultiChain Community Edition methods here, https://mcwrapper.com/supported-methods