Last post Mar 12, 2014 11:31 AM by RunningOutOfUserNames
Mar 03, 2014 05:51 AM|RunningOutOfUserNames|LINK
Using fiddler I can see the call to /signalr/hubs is returning a 404
The project runs fine via VS2012, but once deployed on my local win7 IIS 7.5 machine, retuens the 404
messageHub is undefined
var messageHub = $.connection.startHub;
and in my hub class
public class ourHub : Hub
I'm calling MapHubs in App Start
protected void Application_Start(object sender, EventArgs e)
//Required for SignalR
and I have the RAMFAR (runAllManagedModulesForAllRequests="true">) setting in web.config...
<validation validateIntegratedModeConfiguration="false" />
<add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah" preCondition="managedHandler" />
<add name="ErrorMail" type="Elmah.ErrorMailModule, Elmah" preCondition="managedHandler" />
<add name="ErrorFilter" type="Elmah.ErrorFilterModule, Elmah" preCondition="managedHandler" />
The issue would seem to be around how I define the auto-generated signalr/hubs
It's an asp.net app (not mvc) so the troubleshooting page (https://github.com/SignalR/SignalR/wiki/Faq) seems to state
which neither works in debug through VS or when deployed I've also tried
<script src="/signalr/hubs"></script> (also with the type declaration)
I've searched about and a hotfix has been mentioned http://support.microsoft.com/kb/980368 but the win7 downloads state they're not applicable to my computer...
NB SignalR version is 1.1.3. I've tried this with SignalR2 out of despiration and the issue still is the same, so its not down to the specific version.
I've also downloaded the StockTicker app which again works fine through VS, but upon deployment reports the same underlying issue, because $.connection.stockTickerMini is undefined
many thanks :)
Mar 07, 2014 10:16 AM|andymarksonline|LINK
Have you tried without the auto generated proxy object in JS?
See here :
You don't need to register a reference to signal/hubs then.
I know this doesn't exactly answer your question but it may work.
Mar 12, 2014 11:31 AM|RunningOutOfUserNames|LINK
Sorry for the delay - thanks for the response Andy.
I wasn't aware about doing withouth the auto generated proxies, so went through that exercise with the same end result, leading me to the conclusion that maybe it's not the hubs at all. So therefore unhitched signalR altogether, and re-added via nuget. This
time I wasn;t getting 404 but an error generated in the hub its self (an error nothing to do with SignalR), and once that was sorted, it all hung together in debug and (vitally!) once deployed.