Kaazing.Enterprise 4.1.1

There is a newer version of this package available.
See the version list below for details.
dotnet add package Kaazing.Enterprise --version 4.1.1                
NuGet\Install-Package Kaazing.Enterprise -Version 4.1.1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Kaazing.Enterprise" Version="4.1.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Kaazing.Enterprise --version 4.1.1                
#r "nuget: Kaazing.Enterprise, 4.1.1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Kaazing.Enterprise as a Cake Addin
#addin nuget:?package=Kaazing.Enterprise&version=4.1.1

// Install Kaazing.Enterprise as a Cake Tool
#tool nuget:?package=Kaazing.Enterprise&version=4.1.1                

The Kaazing Enterprise .NET package contains client libraries for the following:

* Creating and using secure robust native WebSocket connections from desktop, mobile, and Xamarin applications

* Communicating with a JMS-compliant messaging system or broker through Kaazing WebSocket Gateway using WebSocket connections from desktop, mobile, and Xamarin applications

* Communicating with a AMQP 0-9-1 messaging system or broker through Kaazing WebSocket Gateway using WebSocket connections from desktop, mobile, and Xamarin applications

This package is compatible with .NET applications for desktop and mobile devices, and Xamarin applications deployed to mobile devices.

Product Compatible and additional computed target framework versions.
.NET net6.0-android was computed.  net7.0-android was computed.  net8.0-android was computed. 
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid is compatible. 
MonoTouch monotouch is compatible. 
Universal Windows Platform uap was computed.  uap10.0 was computed. 
Windows Phone wp81 is compatible.  wpa81 is compatible. 
Xamarin.iOS xamarinios is compatible. 
Xamarin.Mac xamarinmac is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
5.0.3 2,278 12/12/2019
5.0.1 1,336 6/11/2019
5.0.0 2,572 5/16/2018
4.1.7 1,034 6/26/2019
4.1.4 2,122 8/22/2017
4.1.2 2,661 3/23/2016
4.1.1 2,134 3/21/2016
4.1.0 1,508 3/17/2016

What's New

* Updated to .NET Framework 4.5.2

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

* Support for .NET Mobile RFC-6455 (WebSocket)

 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 (https://bugzilla.xamarin.com/show_bug.cgi?id=37624).

* Nuget packaging and delivery for .NET

Known Issues

* tickets#303

 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".

 Workaround this issue by setting the cipher suites in the Kaazing gateway as follows:

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

* tickets#352

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

* tickets#286

 Xamarin WebSocket client will not establish a connection on Android until the INTERNET permission flag is enabled in AndroidManifest.xml. See the folliwng for more information:

 - http://stackoverflow.com/questions/35465102/httpwebrequest-access-denied-on-release-build-xamarin-android

 - https://developer.xamarin.com/recipes/android/general/projects/add_permissions_to_android_manifest/