Build emits outputs to wrong directory on ASP.NET Core

I’m submitting a bug report

• Library Version: 0.22.0

Please tell us about your environment:

• Operating System: Windows 8.1

• Node Version: 6.5.0

• NPM Version: 3.10.9

• Browser: all

• Language: all

Current behavior: Running au build produces the bundles in the ./scripts folder instead of ./wwwroot/scripts in ASP.NET Core projects

Expected/desired behavior:

• au new --here
• Choose 2 (ASP.NET Core)
• Choose 1 or 2 (Babel or TypeScript)
• Choose 1 (No CSS pre-processor)
• Choose 1 (Yes for unit testing)
• Choose 1 (Create project)
• Choose 1 (Install dependencies)
• run au build
• a ‘scripts’ folder is created with the bundles in the current folder, not in the wwwroot folder

• What is the expected behavior? The build output should be in ./wwwroot/scripts This can be fixed after creating the project by changing the build.targets.output in aurelia.json from ‘scripts’ to ‘wwwroot/scripts’

• What is the motivation / use case for changing the behavior? index.html cannot load the bundles (404) and the app does not work

[plwalters]

The fix here for asp.net using --here flag -

1. aurelia.json (all locations) a. Change scripts to wwwroot/scripts a. Change index to wwwroot/index.html
2. run.js a. Change baseUrl from . to ./wwwroot

I’ll try to PR this and test it but if anyone wants to steal that and PR it it is working for me.

[JeroenVinke]

Yep, I think #418 fixed this (aurelia.json script and index properties contain wwwroot now). The baseURL is still incorrect for new apps though, but that is tracked in https://github.com/aurelia/cli/issues/531