Compiler and tooling experience for Razor ASP.NET Core apps in Visual Studio, Visual Studio for Mac, and VS Code.
Перейти к файлу
N. Taylor Mullen ac967397b4 Tactically fix caching compiler issue at TagHelper resolution times
- This changeset should not be ported to VS windows.
- The gist of what this changeset is doing is that at TagHelper resolution time, right before we return results, we call into a compiler utility method that will populate a cache in the TagHelperDescriptor. This cache is known tohave concurrency issues that result in VS4Mac crashing. Therefore to avoid this we pre-populate that cache before any concurrency scenario can happen.

Tactical fix of https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1468241
2022-02-22 10:24:23 -08:00
.devcontainer
.githooks
.github
.vscode
docs
eng Update mpack version in more places 2022-02-11 10:48:50 -08:00
src Tactically fix caching compiler issue at TagHelper resolution times 2022-02-22 10:24:23 -08:00
.editorconfig
.gitattributes
.gitignore
CODE-OF-CONDUCT.md
CONTRIBUTING.md
Directory.Build.props
Directory.Build.targets
LICENSE.txt
NOTICE.txt
NuGet.config
README.md
SECURITY.md
activate.ps1
activate.sh
azure-pipelines-richnav.yml
azure-pipelines.yml
build.cmd
build.ps1
build.sh
clean.cmd
clean.ps1
clean.sh
global.json
restore.cmd
restore.sh
startvs.cmd

README.md

ASP.NET Core Razor Tooling

Razor Tooling is the open-source implementation for the Razor IDE experience in ASP.NET Core. It contains tools for working on Razor ASP.NET Core apps using Visual Studio, Visual Studio for Mac, and Visual Studio Code.

Contributing

All work on Razor Tooling happens directly on GitHub. Both core team members and external contributors send pull requests which go through the same review process. Some of the best ways to contribute are to try things out, file issues, join in design conversations, and make pull requests.

Getting Started with Razor

If you are unfamiliar with ASP.NET Core or Razor, follow the links below to learn more:

Also check out the .NET Homepage for released versions of .NET, getting started guides, and learning resources.

Reporting security issues and bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

Status Build Status

Build Windows Linux MacOS
Debug Build Status Build Status Build Status
Release Build Status Build Status Build Status

These are some other repos for related projects:

Code of conduct

See CODE-OF-CONDUCT.md