{"id":20062,"date":"2018-11-14T12:19:36","date_gmt":"2018-11-14T19:19:36","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/?p=15735"},"modified":"2018-11-14T12:19:36","modified_gmt":"2018-11-14T19:19:36","slug":"asp-net-signalr-2-4-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/asp-net-signalr-2-4-0\/","title":{"rendered":"ASP.NET SignalR 2.4.0"},"content":{"rendered":"<p>We&#8217;ve just shipped the final 2.4.0 version of ASP.NET SignalR, the version of SignalR for System.Web and\/or OWIN-based applications. As we mentioned in a previous post on the <a href=\"https:\/\/devblogs.microsoft.com\/aspnet\/the-future-of-asp-net-signalr\/\">future of ASP.NET SignalR<\/a>, 2.4.0 is a minor release which contains some small bug fixes and updates. The majority of the features and fixes we implemented for ASP.NET SignalR were outlined in the <a href=\"https:\/\/blogs.msdn.microsoft.com\/webdev\/2018\/10\/22\/asp-net-signalr-2-4-0-preview-2\/\">2.4.0 Preview 2 post<\/a>.<\/p>\n<h2 id=\"supportforstackexchangeredis20\">Support for StackExchange Redis 2.0<\/h2>\n<p>In 2.4.0 we&#8217;re adding support for the new 2.0 release of the <a href=\"https:\/\/www.nuget.org\/packages\/StackExchange.Redis\/\">StackExchange.Redis<\/a> package. If you&#8217;re using StackExchange&#8217;s Redis package in your SignalR apps and you want to update to the StackExchange Redis 2.0 version, you&#8217;ll need to remove your existing package reference to <a href=\"https:\/\/www.nuget.org\/packages\/Microsoft.AspNet.SignalR.Redis\">Microsoft.AspNet.SignalR.Redis<\/a>, then add a reference to the new <a href=\"https:\/\/www.nuget.org\/packages\/Microsoft.AspNet.SignalR.StackExchangeRedis\">Microsoft.AspNet.SignalR.StackExchangeRedis<\/a> package.<\/p>\n<p>Once you make the package reference changes, you&#8217;ll also want to replace calls to the <code>UseRedis<\/code> method with <code>UseStackExchangeRedis<\/code>.<\/p>\n<h2 id=\"yourfeedbackiswelcomeandappreciated\">Your Feedback is Welcome and Appreciated<\/h2>\n<p>We recommend you try upgrading to 2.4.0. Your feedback is critical to making sure we produce a stable and compatible update, and has contributed to the continued success of our real-time libraries! You can find details about the release on the <a href=\"https:\/\/github.com\/SignalR\/SignalR\/releases\">releases page<\/a> of the ASP.NET SignalR GitHub repository.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We&#8217;ve just shipped the final 2.4.0 version of ASP.NET SignalR, the version of SignalR for System.Web and\/or OWIN-based applications. As we mentioned in a previous post on the future of ASP.NET SignalR, 2.4.0 is a minor release which contains some small bug fixes and updates. The majority of the features and fixes we implemented for [&hellip;]<\/p>\n","protected":false},"author":2046,"featured_media":21397,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,7256],"tags":[],"class_list":["post-20062","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","category-signalr"],"acf":[],"blog_post_summary":"<p>We&#8217;ve just shipped the final 2.4.0 version of ASP.NET SignalR, the version of SignalR for System.Web and\/or OWIN-based applications. As we mentioned in a previous post on the future of ASP.NET SignalR, 2.4.0 is a minor release which contains some small bug fixes and updates. The majority of the features and fixes we implemented for [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/20062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/2046"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=20062"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/20062\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/21397"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=20062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=20062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=20062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}