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.
* We cannot use the BrowserDebugProxy from the extension folder, that one only works with .net6 app, and it should work with .net6 and .net7, so we should use the inspectURI which will start the correct browserDebugProxy version.
* try to get the inspectUri from the launchSettings.json file, if it cannot be found then use the default one, this will make possible debug the new browserwasm template
* avoiding exception if profiles doesn't exist
* Retrieve debug proxy as part of the build
* Switch vscode:prepublish to run build
* Remove manual retrieveDebugProxy invocation in CI
* Add caching to the download
Remove BlazorDebugProxy from the repo now that it's downloaded on-build
* Constify
* Remove unused require
* Fail fast if download doesn't succeed
* Reorganize some variables
* Move folder instead of individually copying files
* Use Node 10-compliant APIs
* More Node 10 compat workarounds
* Revert "Move folder instead of individually copying files"
This reverts commit 322b02e70f.
* Create target directory after cleaning it
* Download BlazorDebugProxy into subdirectories
[master] Update dependencies from dotnet/aspnetcore
- Coherency Updates:
- Microsoft.Extensions.Configuration.Json: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.Extensions.Logging: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- System.Diagnostics.DiagnosticSource: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- System.Resources.Extensions: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- System.Text.Encodings.Web: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.Extensions.DependencyModel: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.App.Ref: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.BrowserDebugHost.Transport: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.Platforms: from 6.0.0-preview.3.21161.2 to 6.0.0-preview.3.21162.1 (parent: Microsoft.CodeAnalysis.Razor)
- React to aspnetcore breaking changes.
* Add scripts and assets for publishing companion extension
* Adddress feedback from peer review
* Add Azure Pipelines logic
* Update user facing READMEs for companion extension
* Apply suggestions from code review
* Clean up extension naming and add conditional check to builds
* Use single powershell script for version and package
* Remove scripts from packaged extension and fix output path
* Trim out whitespace in version
* Bump version and update condition for jobs
- 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.
Jared Parsons
David Wengier
Allison Chou
Ryan Brandenburg
Fred Silberberg
Thays Grazia
Winston Liu
dotnet-maestro[bot]
Safia Abdalla
Tanay Parikh
N. Taylor Mullen
Ryan Nowak
Ryan Nowak