Compiler and tooling experience for Razor ASP.NET Core apps in Visual Studio, Visual Studio for Mac, and VS Code.
Перейти к файлу
Ryan Brandenburg 5530de5c83 Clean up bad Analyzer references 2022-11-02 09:18:49 -07:00
.devcontainer Merge remote-tracking branch 'compiler/merge-to-tooling' into merge-compiler-no-changes 2022-08-29 11:32:39 -07:00
.github Merge pull request #6968 from dotnet/features/the-merge 2022-10-11 22:36:35 -07:00
.vscode Razor Compiler Codespaces Support (#33) 2022-01-20 10:49:33 -08:00
docs Cleanup Readme 2022-09-13 12:10:55 -07:00
eng Revert "Upgrade VS versions and react to changes" 2022-10-20 12:04:27 -07:00
src Clean up bad Analyzer references 2022-11-02 09:18:49 -07:00
.editorconfig Add a few more things to create a baseline .editorconfig 2022-10-05 20:51:18 +11:00
.gitattributes Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
.gitignore Retrieve BlazorDebugProxy on build (#6081) 2022-02-23 16:10:57 -08:00
.vsconfig Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
CODE-OF-CONDUCT.md Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
CONTRIBUTING.md Clean up markdown warnings (#6179) 2022-03-15 14:24:10 -07:00
Directory.Build.props Merge branch 'main' into features/the-merge 2022-10-03 11:20:14 -07:00
Directory.Build.targets Seperate out Directory.Build.* for compiler and tooling where needed 2022-08-29 12:00:21 -07:00
LICENSE.txt Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
NOTICE.txt Don't change O# dependencies 2022-09-28 16:27:11 -07:00
NuGet.config Revert "ENVDTE" 2022-10-20 12:04:30 -07:00
README.md Rename files to avoid clashes 2022-08-16 12:38:55 -07:00
README_compiler.md Rename files to avoid clashes 2022-08-16 12:38:55 -07:00
SECURITY.md Clean up markdown warnings (#6179) 2022-03-15 14:24:10 -07:00
activate.ps1 Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
activate.sh Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
azure-pipelines-compiler.yml Rename files to avoid clashes 2022-08-16 12:38:55 -07:00
azure-pipelines-compliance.yml Update compliance build step (#6533) 2022-06-24 13:12:33 -07:00
azure-pipelines-integration-dartlab.yml Re-enable IntegrationTests (#6909) 2022-10-11 21:58:39 +00:00
azure-pipelines-richnav.yml Use Powershell task 2022-10-13 16:02:34 -07:00
azure-pipelines.yml Re-enable IntegrationTests (#6909) 2022-10-11 21:58:39 +00:00
build.cmd Fix build.cmd to always pass -restore and -build 2022-09-07 10:06:20 -07:00
build.ps1 Remove dotnet format git hook 2022-08-25 19:26:56 +10:00
build.sh Fixup build issues 2021-11-23 16:03:12 -08:00
clean.cmd Fix @inject intellisense (#949) 2019-08-09 13:13:18 -07:00
clean.ps1 Fix @inject intellisense (#949) 2019-08-09 13:13:18 -07:00
clean.sh Added executable bit to clean shell script (#1841) 2020-04-27 17:13:25 -07:00
global.json Update dependencies from https://github.com/dotnet/arcade build 20221013.2 (#6993) 2022-10-17 21:43:38 +00:00
razor-compiler.sln Rename overlapping projects to .Compiler 2022-08-29 12:00:31 -07:00
restore.cmd Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
restore.sh Add additional razor-compiler files 2021-11-22 11:25:37 -08:00
startvs.cmd Set default for startvs.cmd (#5658) 2021-10-25 09:53:42 -07:00

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