V1 Adapter Migration

When moving from the the original V1 .NET adapter to the new adapter there are several areas that will require attention.

The new adapter no longer supports the .NET Framework

The new adapter targets .NET versions from 6+ and has explicit NuGet packaged versions for each .Net release it supports. Currently this is .NET 6 and .NET 7

By targetting only newer versions of .NET, this has allowed us to leverage the newer built-in features (e.g. Json, WebSockets) therefore removing most of the 3rd party dependencies the adapter previously had. In turn this makes integrating with your own applications easier.

Changes to how you access APIs

To enhance the ability for you to write your own unit tests that effectively mock out the adapter, we have implemented a new service query-like API. You can read more here and this will be covered in the migration samples below.

Once you have access to the API, the invocations are mostly the same as the original adapter.

Several APIs have been removed from the adapter

Lesser used APIs have been removed. This allows us to streamline the adapter and in several cases opens up more efficient methods. For example, we no longer support the Platform API within the .NET adapter. The recommendation is to use the Channels API to communicate with a JavaScript provider which in turn invokes the JavaScript Platform API. There are potential performance advantages in certain circumstances, such as calling multiple Platform APIs in sequence is far more "chatty" than sending a single channels invocation.