title: Aurelia .NET Core - Browser sync not working on .NET Core
body: <p>I followed <a href="http://mobilemancer.com/2016/10/19/aurelia-spa-typescript-dotnet-core/" rel="nofollow noreferrer">this</a> tutorial on how to use Aurelia/Aurelia CLI with .NET Core.</p>
  
  <p>Changes that I had to make:</p>
  
  <ul>
  <li>Had to target a specific version for Microsoft.DotNet.Watcher.Tools, (<strong>dotnet watch run command didn't work</strong>)</li>
  <li>Changed aurelia.json => build => targets => output value from "." to "wwwroot/scripts", (<strong>port:9000 didn't work</strong>, errormessage: "Cannot GET / to the server", port 5000 served by .NET Core worked however).</li>
  <li>tasks => run.js => browsersync => server => basedir value from ['.'] to ['./wwwroot'], (<strong>Fixed browser sync not working on port:9000</strong>, however still doesn't work on port:5000 served by .NET Core)</li>
  </ul>
  
  <p><strong>1. How can I make the Browser sync work on port:5000 served by .NET Core?</strong></p>
  
  <p>It must be something in the run.js file. I have tried:</p>
  
  <pre><code>let serve = gulp.series(
    build,
    done =&gt; {
      browserSync({
          open: false,
          port: 9000,
          logLevel: 'silent',
          proxy: {
          target: 'localhost:5000'
        }
        }, function(err, bs) {
          let urls = bs.options.get('urls').toJS();
          console.log(`Application Available At: ${urls.local}`);
          console.log(`BrowserSync Available At: ${urls.ui}`);
          done();
      });
    }
  );
  </code></pre>
  
  <p>..with no success..</p>
  
  <p><strong>2. Does it matter if I develop on port:5000 or port:9000?</strong></p>
  
  <p><strong>3. What's the point in hosting Aurelia in .NET Core?
  Should I only use .NET Core for WepAPI etc?</strong></p>