Migrate from the .NET Framework adapter

When moving from the the original OpenFin adapter for .NET Framework to the adapter for .NET 6+, there are several areas that require attention.

The .NET 6+ adapter does not support .NET Framework

This adapter implementation targets .NET versions 6 and later, and has explicit NuGet packaged versions for each .NET release it supports. Currently there are packages for .NET 6 and .NET 7.

By targeting only newer versions of .NET, the adapter can leverage the newer built-in features (such as JSON and WebSockets), therefore removing most of the 3rd party dependencies that the adapter for .NET Framework 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 about Runtime services. The migration samples illustrate using it.

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

Several APIs have been removed from the adapter

Less-often used APIs have been removed. This enables streamlining the adapter and in several cases opens up more efficient methods.
For example, the .NET 6+ adapter does not directly support the Platform API.
OpenFin recommends that you use the Channel API to communicate with a JavaScript provider, which in turn invokes the JavaScript Platform API.
There are potential performance advantages in certain circumstances. For example, calling multiple Platform API methods in sequence is far more "chatty" than sending a single Channel API invocation. The .NET 6+ adapter's reduces the need for extra invocations.