Since he (she? they?) has gone into excellent depth, I'll only cover what I did differently to get it to work in a non-Windows environment (spoiler alert: not much!)
ASP.NET Core 1.0 RC2
YeomanTo create ASP.NET boilerplate code, we use Yeoman (installed via npm). Type:
Then Choose "Web Application" because conveniently enough, MVC now is Web API with ASP.NET Core!
Check this page for installation tips: https://docs.asp.net/en/latest/client-side/yeoman.html#install-node-js-npm-and-yeoman
Visual Studio Code
- C# syntax error highlighting
- assist with "using" statements
- Integrated debugging - although I lucked out and didn't need it, it does work very well and having that on tap has a value which cannot be overstated
Building Visual Studio Code ... from codeMost folks will install direct from a download, but if you're like me and want to build vscode from source, be advised - I found no "install" mechanism when building Visual Studio code.
For convenience, after building Visual Studio Code I made a $PATH discoverable symlink called "vscode" to easily start it anywhere. I suggest you do the same
.vscode folder & tasks.json
- launch.json - among other things, this feeds the debugger for what configurations you'd like to launch & debug
- tasks.json - when using vscode's integrated build feature (ctrl-shift-B on non Macs) it reaches out to this file to determine what to do.
Don't forget, Visual Studio isn't here to help you with gulp tasks, so you'll have to run them manually (you'll want to run gulp copy-deps and gulp min) after you've done a proper npm install. Remember, a proper npm install won't work until your package.json is sorted out.