dotNetify

• fixed issue #68: exception middleware broke in the last release.
• fixed middleware call type value for Update_VM calls.

This release provides the following updates:

• new APIs to support reactive programming.
• new capability to create dynamic, reactive properties (issue #53).
• new capability to register dynamic view model types.
• view models are no longer required to inherit from BaseVM (issue #51).
• fix the race condition between PushUpdates and Changed API calls.

Breaking changes:

• the Observable class is renamed to ObservableObject to avoid name clash with System.Reactive.Linq.
• the Ignore attribute is moved outside BaseVM.

Note for ASP.NET Framework users:
The existing DotNetify package is deprecated, and is replaced with DotNetify.SignalR.Owin. This new package depends on DotNetify.Core which targets .NET Standard 2.0, which means that your ASP.NET project must target at least .NET Framework 4.6.1.

This release addresses the following issues found in dotnetify-react.router during development of React SPA template:

• Fixed RouteTarget component to use local React reference.
• Fixed RouteLink component to pass the anchor click event.
• Made execution of routing asynchronous to allow click event to complete first.
• Added new router API $routeTo to allow UI script to route programmatically.

This release provides the integration with the latest SignalR for ASP.NET Core 2.0 (currently alpha2).

Upgrade from Previous Version

Both the client and server must be upgraded. Your ASP.NET Core Web project must target .NET Core 2.0. In Startup.cs, update the call UseSignalR() to:

UseSignalR(route => route.MapDotNetifyHub());

The latest SignalR for .NET Core is not compatible with SignalR for .NET Framework. While dotNetify client-side library can be used for both, make sure the client matches the server it connects with. The .NET Core library is assumed by default. To switch to the other library, add this to the entry point:

import signalR from 'dotnetify/dist/signalR-netfx';  
dotnetify.hubLib = signalR;

If you use Webpack with babel loader, the loader will need exclude: /node_modules/ to avoid bundling error.

Transport Fallback

SignalR for .NET Core no longer provides transport fallback, i.e. falling back to SSE or HTTP long polling if WebSocket is not supported. However, this feature is now being fulfilled by dotNetify. By default, dotNetify will fall back to long polling when WebSocket fails. The fallback order and type can be configured as below:

dotnetify.hubOptions = { transport: ["webSockets", "serverSentEvent", "longPolling"] };

Note that SSE has been observed in some environments to exhibit long delay during the initial connection. The exact cause is still unknown.

Connection State Management

You can receive notification when the connection state changed by providing a handler function:

dotnetify.connectionStateHandler = (state) => { /* handle state changed event */};

The state's possible values are: "connecting", "connected", "reconnecting", "disconnected" and "terminated".

If the connection gets disconnected, as part of its resiliency feature, dotNetify will automatically attempt to reconnect indefinitely, with the delay between attempts of 2 seconds, 5 seconds, and then every 10 seconds afterwards. These can be configured as below:

dotnetify.hub.init();
dotnetify.hub.reconnectDelay = [5, 30];
dotnetify.hub.reconnectRetry = 10;

The above configuration indicates that the reconnect attempt is limited to 10 times after every disconnected event, with initial delay of 5 seconds and then every 30 seconds afterwards. When the retry attempt is exhausted, the "terminated" state is triggered.

This release's major aim is to support React Native with the following update:

• include a custom version of SignalR JS client based on v.2.2.2 that has no hard dependencies to jQuery and window variable.
• remove hard dependencies to full jQuery, window variable and React DOM from dotNetify core module; no more need to include jQuery plugin in the webpack configuration.
• include jQuery shim that has dependency only to jQuery-deferred npm library.
• add new API dotnetify.connectionStateHandler to provide connection state changed events.
• add new API dotnetify.hubServerUrl to specify server URL.

Other misc. updates:

• decouple signalR hub code to a separate module to lay the groundwork for supporting the new version of SignalR client for .NET Core.
• include Typescript definition files ( issue #46 ).

v2.2.1-pre:

• Unbundled ASP.NET 4.5 library.
• Fixed runtime error on ASP.NET Core web project targetting .NET Framework.

v.1.2.0:

• ASP.NET 4.5 library that has parity with v2.2.1-pre.

v2.0.5-beta npm

• fixed issue #28: subsequent routing failing to trigger when having the same template but different parameter.
• fixed issue #34: IE polyfill for dispatching event in routing plugin.
• modified the connect API to allow configuring headers for things such as JWT authentication.
• added capability to handle server-side exception.
• added dotNetify.hubPath to configure signalR base path.
• updated signalR client to v2.2.2.

v2.2.0-pre nuget

• nugets targetting .NET Standard 1.6 and .NET 4.6.2.
• fixed issue #30: provide configurable VM controller cache expiration.
• added basic dependency injection in the library targetting .NET 4.6.2.
• added middleware and view model filter pipelines (issue #29).
• added JWT authentication middleware.
• added authorize filter.

Beta for ReactJS integration.

• Fixed bug related to mobile offline support.

v1.1.0

• added mobile hybrid app support.
• various bug fixes and enhancements.

v.2.0.0-pre

• ported to ASP.NET Core.
• added webpack support.

Change since initial beta version:

• Added Typescript support.

Target release date: Q1 2016.

Initial beta version. Target release date: Q1 2016.