- Added the `.vscode-test` to `.gitignore` because that's the VSCode folder that gets created when dynamically downloading VSCode for CI purposes.
- Migrated functional tests to use the non-deprecated VSCode functional testing APIs. This involved creating a runTest file to control downloading VSCode and passing in appropriate parameters as well as creating an index that discovers tests that should be run.
- Changed functional tests to operate on the existing Razor testapps (instead of the old ones).
- Updated the "default" completion tests to be latest Razor/Blazor.
- Added VSCode launch configurations to enable easy debugging via F5.
aspnet/AspNetCore#13494
- This changeset adds the following:
- src/Razor/src/Microsoft.AspNetCore.Razor.VSCode - Razor VSCode extension library
- src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.Extension - Razor VSCode extension bootstrapper
- Added a `README.md` into the `Microsoft.AspNetCore.Razor.VSCode.Extension` to describe its purpose.
- Moved old Razor VSCode project bits from `npm` to `yarn`
- Added a global .vscode folder to allow having VSCode open at AspNetCore-Tooling root yet still be able to ctrl + f5 the extension
- Expanded the bootstrapper extension project (`Microsoft.AspNetCore.Razor.VSCode.Extension`) to have new commands to make working with projects in experiemental instances easy. Prior to this we relied on a node.js script that were unsupported to magically wire things together. As part of the merging of this repo I had to find an alternate route to do that.
- Added a Razor global tslint file which each VSCode project inherits from
- Added a Razor global tsconfig file which each VSCode project inherits from
- Updated npmproj's to ensure build incrementalism works.
aspnet/AspNetCore#13494
This is a bit of a rework of how we initially set this up, but with more
forethought to how this will work in the project system. I have not yet
surfaced this through VS.
My immediate next step is to light up the component integration tests
and something like this is on the critical path to get that work since
we need a way to specify in tests that a document should be treated as
a component.
Ryan Brandenburg
N. Taylor Mullen
Ryan Nowak
Ryan Nowak