Geek Answers Handbook

Failed to register routes in SignalR 2.0.0

I decided to upgrade to the latest version of signalr, but I ran into a few problems. First of all, the path to registering routes has completely changed; so I tried to do it as suggested by this link http://www.asp.net/vnext/overview/latest/release-notes#TOC13 .

The problem is that although I add

<appSettings> <add key="owin:AppStartup" value="xxx.Startup, App_Code"/> </appSettings>

in web.config Configuration is not called at all. Does anyone know what I'm doing wrong?

+7
owin routes signalr
source share
5 answers

Decision!

 <appSettings> <add key="owin:AppStartup" value="MyNameSpace.Startup, MyNameSpace" /> <add key="owin:AutomaticAppStartup" value="true" /> </appSettings> <system.web> <httpHandlers> <add verb="*" path="*" type="Microsoft.Owin.Host.SystemWeb.OwinHttpHandler, Microsoft.Owin.Host.SystemWeb"/> </httpHandlers> </system.web> <system.webServer> <handlers> <add name="Owin" verb="*" path="*" type="Microsoft.Owin.Host.SystemWeb.OwinHttpHandler, Microsoft.Owin.Host.SystemWeb"/> </handlers> </system.webServer>
+5
source share

I was able to get 2.0 beta by working on

  • Removing all links to an older version of SignalR, i.e. library removal and double check / bin

  • Installed SignalR 2.0.0-beta2 through the Install-Package Microsoft.AspNet.SignalR -Pre Manager console Install-Package Microsoft.AspNet.SignalR -Pre

  • Following the instructions for migrating from 1.x to 2.0 described in the ops link

  • And the most important project configuration change to use the local IIS web server instead of Visual Studio Developer Server (Cassini).

Additional information in the question / answer I posted here

+2
source share

For me, the answer was that this DLL was missing:

 Microsoft.Owin.Host.SystemWeb.dll

It was omitted by my build process. It seems that it should be present in the bin folder of the Asp.Net site for the Configuration method to call.

+1
source share

Is this a site? If this is a website, the assembly for the website is generated dynamically, so you cannot determine the fully qualified name of your startup class like this. Instead, try adding an assembly level attribute to your code like this, and see if your Startup.Configuration is called.

[build: OwinStartup (typeof (start))]

0
source share

By default, it will search for the Startup file; so the only thing I needed to do was create a Startup class in the Assembly-name.Startup .

The namespace must follow the pattern above so that you can find the launch class

0
source share

More articles:


All Articles