Just a second...

.NET

The .NET API is provided as a package compatible with Microsoft® .NET Standard 2.0.

Get the .NET SDK from NuGet:

Use the following .NET CLI command:
dotnet add package Diffusion.Client -v 6.2.0

Get the .NET SDK:

These files are also located in your Diffusion™ server installation:
diffusion_directory/clients/dotnet

Capabilities

To see the full list of capabilities supported by the .NET API, see Feature support in the Diffusion API.

Support

Table 1. Supported platforms and transport protocols for the client libraries
Platform Minimum supported versions Supported transport protocols
.NET Microsoft .NET Standard 2.0

WebSocket

Resources

Using

Certificates

Diffusion .NET clients use certificates to validate the security of their connection to the Diffusion server. The client validates the certificate sent by the Diffusion server against the set of certificates trusted by the .NET Framework.

If the certificate sent by the Diffusion server cannot be validated against any certificates in the set trusted by the .NET Framework, you must set up a trust store for the client and add the appropriate certificates to that trust store.

Diffusion is authenticated using the certificates provided by your certificate authority for the domain you host the Diffusion server on.

  1. Obtain the appropriate intermediate certificate from the certificate authority.
  2. Use the Microsoft Management Console to import the certificate into the Trusted Root Certification Authorities folder. For more information, see https://msdn.microsoft.com/en-us/library/aa738659(v=vs.110).aspx
Writing good callbacks
The .NET client library invokes callbacks using a single inbound thread. Callbacks for a particular session are called in order, one at a time. Consider the following when writing callbacks:
  • Do not sleep or call blocking operations in a callback. If you do so, other pending callbacks for the session are delayed. If you must call a blocking operation, schedule it in a separate application thread.
  • You can use the full Diffusion API to make other requests to the server. If you want to make many requests based on a single callback notification, be aware that Diffusion client flow control is managed differently in callback threads. Less throttling is applied and it is easier to overflow the servers by issuing many thousands of requests. If you have a lot of requests to make, it is better to schedule the work in an application thread.
Regular expressions

The .NET client uses a different regular expression engine to the Diffusion server. Some regular expressions in topic selectors are evaluated on the client and others on the Diffusion server. It is possible that topic selectors that include complex or advanced regular expressions can behave differently on the client and on the Diffusion server.

For more information, see Regular expressions.