OK – this didn’t take me that long but there were some pitfalls reading what I could online between MS and Umbraco and Stackoverflow.
The article is brief and to the point but I’ll flesh out when I do a full article on actually using SignalR on the front end of the website. Right now I’m busy building that site!
1. I am using Umbraco Cloud 7.11.1, we have three projects in our solution. The CORE, The WEB and Published Models project that stores the strongly type models generated by the CMS Models Builder
2. Install Nuget Package – install-package Microsoft.AspNet.SignalR (MAKE SURE YOU DO NOT INSTALL THE LATEST VERSION (2.2.3) THAT WILL BREAK THE BACK OFFICE – INSTALL VERSION 2.2.1)
3. Add/Edit as appropriate the following to your web.config in your WEB project
<add key=”umbracoReservedPaths” value=”~/umbraco,~/install/,~/signalr/” />
<add key=”owin:appStartup” value=”YOUR_NAME_FOR_IT” />
3. Create a Startup.cs in your CORE project – I put ours in a folder called Startup just to be neat
[assembly: OwinStartup(“YOUR_NAME_FOR_IT”, typeof([YOUR NAMESAPNE TO THE Startup.cs].Startup))]
public class Startup : UmbracoDefaultOwinStartup
public override void Configuration(IAppBuilder app)
4. Set up a breakpoint on base.configuration(app) to make sure it fires when you run debug
That’s it for this week – I will definitely be following up with a full article using SignalR on the front end in the near future.