Since integrating our repos, there have been a number of changes in PRs that touch the encoding of the file, adding or removing a BOM as the editor in question decides. I've standardized on UTF-8 with BOM, as we do in roslyn, and put it in the .gitattributes so it should hopefully stay consistent.
* Remove razor-compiler.sln from root directory
* Move Razor.sln and Razor.Slim.slnf into root directory
* Put all projects from razor-compiler.sln into Razor.sln, with same solution folder layout
* Fix builds and docs
* Remove a couple of redundant files in the src\Razor folder
- SourceBuild doesn't care about NodeJS projects. Added a `BuildNodeJs`flag to correspond with AspNetCore's `BuildNodeJs` flag that controls when to include NodeJS projects (doesn't during SourceBuild).
aspnet/AspNetCore#13494
- For simplicity put the unit tests in the test folder to align with all other types of test projects.
- Converted unit tests to use `yarn` and `jest`.
- Added a `Run Unit Tests` launch configuration so we can F5 in VSCode to easily debug Razor VSCode unit tests.
- Hooked new npmproj test projects into the build.
aspnet/AspNetCore#13494
- In preparation for merging the Razor VSCode extension I've added support for npmproj files. I tried to maintain the same functionality that AspNetCore offers for its npmproj support.
- Added an extra `--ignore-engines` check to `yarn install` in preparation for VSCode's extension model. They expect there to be a vscode engine in the package.json that yarn doesn't understand.
aspnet/AspNetCore#13494
This change adds a set of workarounds that we need to enable publishing to
BAR from this repo.
1. Workaround the attempt to call the Execute task on every project
2. Move symbol publishing to its own step so that it keeps happening
3. Reenable BAR publishing
Allison Chou
Fred Silberberg
David Wengier
Ryan Brandenburg
Chris Sienkiewicz
David Barbet
Sam Harwell
John Luo
N. Taylor Mullen
Ryan Nowak
Ryan Nowak