Edited Unassigned: Upgrade System.Web.Http.SignalR project's SignalR.Core package to the latest. [1102]

__Scenario__:
User would like to use HubController<THub> with Web API. So, the user installs "Microsoft.AspNet.WebApi.SignalR" package.

__Issue__:
The latest publicly released stable version is 1.1.2. After making changes to my ValuesController to inherit from HubController<>, I wasn't able to hit "http://server/api/values". Later I figured out that there were assembly loading failures because of which the controller probing did not find any controllers. This assembly loading failure is due to System.Web.Http.SignalR depending on 1.0.0 whereas I had 1.1.0. This issue is one more scenario for fixing the bug # 1075.

__Impact__:
Low as there is a workaround. But the experience is bad due to no easy way of figuring out assembly loading failure due to bug # 1075.

__Workaround__:
Have assembly binding to forward to newer version
```
<dependentAssembly>
<assemblyIdentity name="Microsoft.AspNet.SignalR.Core" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="0.0.0.0-1.0.0.0" newVersion="1.1.0.0" />
</dependentAssembly>
```

__Expected__:

Currently System.Web.Http.SignalR project has the following dependency:
```
<package id="Microsoft.AspNet.SignalR.Core" version="1.0.0" targetFramework="net45" />
```

We need to upgrade it to the latest package.