Fixed an issue where an exception was thrown saying either Object reference not set to an instance of an object or Unable to read data from the transport connection: Network subsystem is down (enterprise.dotnet.client/91)

The cipher suites enabled out-of-the-box in Kaazing Gateway are not compatible with WebSocket native connections for the Xamarin .NET client. TLS connections will fail with a warning stating "protocol is disabled or cipher suites are inappropriate" or "failure to negotiate cipher suites" (tickets/303)

Workaround: Set the cipher suites in the Kaazing gateway as follows:

            
<service-defaults>
  <accept-options>
    <ssl.ciphers>DEFAULT,!RC4</ssl.ciphers>
  </accept-options>
</service-defaults>
            
          

JMS MapMessage Maximum/Minimum values may be rounded during conversion between different .NET platforms and among other clients (tickets/352)

Workaround: Test your particular usage in your particular environment

Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml (tickets/286)

Workaround: See the following for more information:

• HttpWebRequest: Access denied on release build - Xamarin (Android)
• Add Permissions to Android Manifest

.NET Framework 4.6.2 or higher

Fixed an issue where closing the connection during auto-reconnect did not actually result in the connection being terminated. After this fix, if you close the connection in the connection exception handler, the connection will terminate and the client will not automatically attempt to reconnect. Otherwise, if you take no action, the client will attempt to automatically reconnect. (enterprise.gateway/819)

The cipher suites enabled out-of-the-box in Kaazing Gateway are not compatible with WebSocket native connections for the Xamarin .NET client. TLS connections will fail with a warning stating "protocol is disabled or cipher suites are inappropriate" or "failure to negotiate cipher suites" (tickets/303)

Workaround: Set the cipher suites in the Kaazing gateway as follows:

            
<service-defaults>
  <accept-options>
    <ssl.ciphers>DEFAULT,!RC4</ssl.ciphers>
  </accept-options>
</service-defaults>
            
          

JMS MapMessage Maximum/Minimum values may be rounded during conversion between different .NET platforms and among other clients (tickets/352)

Workaround: Test your particular usage in your particular environment

Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml (tickets/286)

Workaround: See the following for more information:

• HttpWebRequest: Access denied on release build - Xamarin (Android)
• Add Permissions to Android Manifest

.NET Framework 4.6.2 or higher

Added support for .NET Core 2.0 and .NET Standard 2.0, which allows .NET clients to run on Linux

The cipher suites enabled out-of-the-box in Kaazing Gateway are not compatible with WebSocket native connections for the Xamarin .NET client. TLS connections will fail with a warning stating "protocol is disabled or cipher suites are inappropriate" or "failure to negotiate cipher suites" (tickets/303)

Workaround: Set the cipher suites in the Kaazing gateway as follows:

            
<service-defaults>
  <accept-options>
    <ssl.ciphers>DEFAULT,!RC4</ssl.ciphers>
  </accept-options>
</service-defaults>
            
          

JMS MapMessage Maximum/Minimum values may be rounded during conversion between different .NET platforms and among other clients (tickets/352)

Workaround: Test your particular usage in your particular environment

Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml (tickets/286)

Workaround: See the following for more information:

• HttpWebRequest: Access denied on release build - Xamarin (Android)
• Add Permissions to Android Manifest

.NET Framework 4.6.2 or higher

Bug fixes.

The cipher suites enabled out-of-the-box in Kaazing Gateway are not compatible with WebSocket native connections for the Xamarin .NET client. TLS connections will fail with a warning stating "protocol is disabled or cipher suites are inappropriate" or "failure to negotiate cipher suites" (tickets/303)

Workaround: Set the cipher suites in the Kaazing gateway as follows:

            
<service-defaults>
  <accept-options>
    <ssl.ciphers>DEFAULT,!RC4</ssl.ciphers>
  </accept-options>
</service-defaults>
            
          

JMS MapMessage Maximum/Minimum values may be rounded during conversion between different .NET platforms and among other clients (tickets/352)

Workaround: Test your particular usage in your particular environment

Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml (tickets/286)

Workaround: See the following for more information:

• HttpWebRequest: Access denied on release build - Xamarin (Android)
• Add Permissions to Android Manifest

.NET Framework 4.5.2 or higher

Updated URLs used in demos

The cipher suites enabled out-of-the-box in Kaazing Gateway are not compatible with WebSocket native connections for the Xamarin .NET client. TLS connections will fail with a warning stating "protocol is disabled or cipher suites are inappropriate" or "failure to negotiate cipher suites" (tickets/303)

Workaround: Set the cipher suites in the Kaazing gateway as follows:

            
<service-defaults>
  <accept-options>
    <ssl.ciphers>DEFAULT,!RC4</ssl.ciphers>
  </accept-options>
</service-defaults>
            
          

JMS MapMessage Maximum/Minimum values may be rounded during conversion between different .NET platforms and among other clients (tickets/352)

Workaround: Test your particular usage in your particular environment

Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml (tickets/286)

Workaround: See the following for more information:

• HttpWebRequest: Access denied on release build - Xamarin (Android)
• Add Permissions to Android Manifest

.NET Framework 4.5.2 or higher

.NET client is now available via Nuget (roadmap/388) Learn more

Updated to .NET Framework 4.5.2 (tickets/377)

This allows the client to directly use native Websocket APIs, if provided by the .NET runtime.

.NET client now supports native WebSocket (RFC-6455) protocol (tickets/377)

This provides native Websocket support when deployed to Windows mobile devices or when cross compiled to mobile devices via Xamarin. Without Kaazing’s libraries, these runtimes do not support native WebSocket or have buggy implementations (e.g. see this Xamarin bug)

The cipher suites enabled out-of-the-box in Kaazing Gateway are not compatible with WebSocket native connections for the Xamarin .NET client. TLS connections will fail with a warning stating "protocol is disabled or cipher suites are inappropriate" or "failure to negotiate cipher suites" (tickets/303)

Workaround: Set the cipher suites in the Kaazing gateway as follows:

            
<service-defaults>
  <accept-options>
    <ssl.ciphers>DEFAULT,!RC4</ssl.ciphers>
  </accept-options>
</service-defaults>
            
          

JMS MapMessage Maximum/Minimum values may be rounded during conversion between different .NET platforms and among other clients (tickets/352)

Workaround: Test your particular usage in your particular environment

Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml (tickets/286)

Workaround: See the following for more information:

• HttpWebRequest: Access denied on release build - Xamarin (Android)
• Add Permissions to Android Manifest

.NET Framework 4.5.2 or higher