dotNetify changelog

Changelog History

Page 1

• v3.6.1

  November 29, 2019

  🐛 Bug Fixes

  • 🛠 Fix auth middleware failure when using MessagePack protocol (#225).
  • 🛠 Fix master view model not participating in the view model filter pipeline (#226).

• v3.6

  November 25, 2019

  🔋 Features

  • 👌 Support SignalR using System.Text.Json serialization (#220).
  • Add hubOptions.connectionBuilder settings to support configuring MessagePack (#221).
  • 👌 Support CRUD APIs passing collection of items.

  🐛 Bug Fixes

  • 👻 Defer registration of entry assembly until it's confirmed there's no other assembly, to avoid exception being thrown prematurely if the entry assembly contains no view model.

• v3.5

  October 01, 2019

  🚀 This release provides a better hub proxy class abstraction, which allows important improvements to the library: multi-hub support (for realizing micro-frontend pattern) and capacity for different hub proxy implementations (e.g. local/client-side view model, communication using web API instead of SignalR).

  🔋 Features

  • Add createHub API to create a new dotNetify hub client.

  • Add connectHandler API to intercept view model connect call to provide the opportunity to switch hub server.
    Doc: https://www.dotnetify.net/core/api/connection

  • ➕ Add "local mode" connect option to support client-side view model.
    Doc: https://www.dotnetify.net/core/api/localmode

  • ➕ Add "web API mode" connect option to access view model through Web API.
    Doc: https://www.dotnetify.net/core/api/webapimode

  • ➕ Add useConnect hook.

  • ➕ Add routing support for web components.

  • Automatically call AddMemoryCache() if the service isn't registered.

  🐛 Bug fixes

  • #201 Fix redirect with root "/".

• v3.4

  July 11, 2019

  🚀 This release adds the following features:

  • ➕ Add a new MulticastVM "Requested' event to notify of requests made to the view model.
  • Include the responses to view model requests in the middleware/filter pipelines.
  • ➕ Add support to switch hub server URL after the first connection (#192).
  • ➕ Add a new method to configure VMSerializer.SerializerSettings (#195).

  🐛 Bug fix:

  • 🛠 Fix CRUD API where the client only retains the last item key received from the view model.

• v3.3.1

  November 28, 2018

  🚀 This release provides the following new features:

  • 🚦 .Addition of .NET client to DotNetify.SignalR library to let .NET applications communicate with SignalR .NET Core hub server (#102). Note: SignalR .NET Framework is not supported.
    

  Doc: http://dotnetify.net/core/api/dotnetclient
  Demo: https://github.com/dsuryd/dotNetify/tree/master/Demo/DotNetClient

  • MapDotnetifyHub extension method can accept HttpConnectionDispatcherOptions configuration options (#137).
  • 👉 New dotNetify configuration method UseJsonSerializerSettings to control how view model data is serialized (#105).

  ⚡️ Other updates:

  • 🛠 Fixed VMSerializer from throwing an exception when serializing JArray objects (#149).
  • ⚡️ Updated support for React Native (#7, #8, #9).
  • 🛠 Fixed routing to work with an empty URL pattern (#26).

• v3.2

  October 25, 2018

  🚀 This release provides client-side library that integrates with Vue.js framework (#49).

• v3.1

  September 30, 2018

  🚀 This release provides the following new features:

  • New view model base class MulticastVM to allow sharing of view model instances with a group of clients, including the capability to push direct messages to specific clients (#58).
    

  Doc: http://dotnetify.net/core/api/multicast
  Demo: http://dotnetify.net/core/examples/chatroom

  • New injectable interface IConnectionContext to provide access to SignalR connection ID and HTTP info of the calling connection (#108).
  • New asynchronous Reactive APIs SubscribeToAsync and SubscribedByAsync (#120).
  • ⚡️ New PushUpdates overload to force updates on view models sharing the same connection with the calling view model, and that returns a boolean true to support fluent chaining (#120).
  • 👍 Allow for middlewares to overwrite data for Response_VM (#111).

• v3.0.1

  May 31, 2018

  🚀 This is an official release of dotNetify for ASP.NET Core.

  • ↔ Integrates with SignalR v1.0 release for .NET Core 2.1.
    ⬆️ (both client and server must be upgraded; must target .NET Core 2.1)

• v3.0.0

  April 13, 2018

  🚀 This release provides the following new features:

  • ⬆️ Integration with SignalR .NET Core v1.0.0-preview2-final ( both client and server must be upgraded ).
  • 🆕 New reactive APIs AddInternalProperty, SubscribedBy and Unsubscribe.
  • 👌 Support for ASP.NET DI Scoped lifetime (services created once per connection).

  ⚡️ Other updates:

  • Prevent value sent by client from getting included in the response if the property type is an array.
  • 👻 Defer registration exception being thrown until initial view model access (dsuryd/dotnetify-react-demo-vs2017#15).

• v3.0.0-pre

  April 13, 2018

  🚀 This release provides the following new features:

  • ⬆️ Integration with SignalR .NET Core v1.0.0-preview2-final ( both client and server must be upgraded ).
  • 🆕 New reactive APIs AddInternalProperty, SubscribedBy and Unsubscribe.
  • 👌 Support for ASP.NET DI Scoped lifetime (services created once per connection).

  ⚡️ Other updates:

  • Prevent value sent by client from getting included in the response if the property type is an array.
  • 👻 Defer registration exception being thrown until initial view model access (dsuryd/dotnetify-react-demo-vs2017#15).

• 1
• 2
• Next ›
• Last »