tag:support.appharbor.com,2010-11-23:/discussions/problems/62378-signalr-21-not-workingAppHarbor: Discussion 2018-10-19T03:07:11Ztag:support.appharbor.com,2010-11-23:Comment/341564252014-08-15T15:52:18Z2014-08-15T15:52:18ZSignalR 2.1 not working<div><p>Did you enabled "File System write access" in your application
settings?</p></div>balexandretag:support.appharbor.com,2010-11-23:Comment/341564252014-08-15T16:23:50Z2014-08-16T13:22:50ZSignalR 2.1 not working<div><p>I did yes, but sadly it didn't help.</p></div>kustudtag:support.appharbor.com,2010-11-23:Comment/341564252014-08-15T17:06:13Z2014-08-15T17:06:13ZSignalR 2.1 not working<div><p>Hi,</p>
<p>It seems like your build doesn't contain any of the SignalR
binaries - only the metadata/xml files. It's likely being ignored
by your git repository's <code>.gitignore</code> file. I think
adding the required binaries will resolve the issue. Also see
<a href=
"http://stackoverflow.com/questions/8941595/signalr-signalr-hubs-giving-404-error">
this discussion</a> about the same issue.</p>
<p>You can always download the build output to verify that the
files are actually being copied to the build artifact as expected.
The link to the build artifact can be found on the build log
page.</p>
<p>I'd recommend using AppHarbor's build infrastructure to compile
the application. It's currently being deployed as-is because
there's no solution file, and that makes errors like these more
likely to happen at runtime as opposed to getting a more usable
build failure.</p>
<p>Let me know if this doesn't help resolve the issue.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/341564252014-08-16T13:57:40Z2014-08-16T13:57:40ZSignalR 2.1 not working<div><p>Awesome Rune, thanks for your help.</p>
<p>It was my fault with missing packages, as you stated. Set it to
use NuGet package restore and all works fine.</p>
<p>Thanks!</p></div>kustud