title: Asp.Net Core SignalR + Angular 6 issue
body: <p>I have a WebApi that was made using <code>Asp.net Core 2.0</code> and consuming this API an <code>Angular 5</code> App. Now I'm making a new version of this App using <code>Angular 6</code>.</p>
  
  <p>In this Web API I use <code>SignalR 1.0.0-alpha-final</code> and in the Angular 5 app I use <a href="https://www.npmjs.com/package/@aspnet/signalr-client" rel="nofollow noreferrer">this</a> as client <code>"@aspnet/signalr-client": "^1.0.0-alpha2-final"</code>.</p>
  
  <p>In the old Angular App everything works fine as intended. My problem is that I can use this package on the new version of my app:</p>
  
  <pre><code>npm ERR! code ELIFECYCLE
  npm ERR! errno 1
  npm ERR! @aspnet/signalr-client@1.0.0-alpha2-update1 install: `echo "This package has been deprecated. Use '@aspnet/signalr' instead." &amp;&amp; exit 1`
  npm ERR! Exit status 1
  npm ERR!
  npm ERR! Failed at the @aspnet/signalr-client@1.0.0-alpha2-update1 install script.
  npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  </code></pre>
  
  <p>Then I try to use the recommended version, I follow <a href="https://www.c-sharpcorner.com/article/getting-started-with-signalr-using-aspnet-co-using-angular-5/" rel="nofollow noreferrer">this article</a> and everything runs OK on the Angular 6 App side, but it never actually connects to the Hub. this is the message I get when running my local Angular APP:</p>
  
  <pre><code>Access to XMLHttpRequest at 'http://localhost:27081/hub/notification/negotiate?jwttoken=the_token_here' from origin 'http://localhost:4200' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
  </code></pre>
  
  <p>It's not a real CORS problem, I made the WebAPI and and Angular APP run in the same domain and I never had CORS problem in my old App. I have the right Cors policies to allow localhost to use the api.</p>
  
  <p>It's weird that the client added <code>negotiate</code> to the connection URL and even If I make my hub answer in this address I get error 400 with this message: <code>Connection ID required</code></p>
  
  <p>I do believe that this Client Library was made to another version than the one I have on the server, since the client and server has to follow the same version.</p>
  
  <p>I tried using the node_modules from the older Angular App but I cannot get it to compile.. I don't know what to do. Has anyone experienced this issue and managed to solve? Any tips? I can't update the version on the WebAPI or I'll make the current App stop working.</p>
  
  <p>Thanks for any help</p>