I’ve made updates to my ‘hub’. Specifically, I’ve added a few new methods. It works fine when I debug within VS 2012. However, when I publish it to my local IIS the signalr/hubs is still generating the old proxy hub. The new methods aren’t listed.
To ensure it wasn’t an older version of the assembly, I ran it through ILSpy and I can see the new methods.
I’ve tried something minor, modifying the HubName attribute to see if even that change would be reflected in the new proxy hub. It isn’t.
Any thoughts on how to force the signalr/hubs url to generate the proper proxy? I’ve tried adding ?120 etc onto the end to see if it’s cached, it didn’t make any difference.
The issue was that the site was being deployed as a sub-application. It has another application sitting above it so the url for the signalr/hubs that we copied from the samples was wrong for our build. We needed it to be relative, so adding the ~ onto the front fixed the issue.