a7c635f6de
We observed a hang during solution load because `VisualStudioEditorDocumentManager` retrieves the `IVsRunningDocumentTable` service in its constructor. When this constructor is called on a background thread, it results in an implicit marshal to the UI thread in order to retrieve the service and QI for its COM interface. This change fixes that issue delaying the request for `IVsRunningDocumentTable` until it is needed and running on the UI thread. In addition, `VisualStudioFileChangeTrackerFactory` had a similar issue but with `IVsAsyncFileChangeEx`. Because `IFileChangeTrackerFactory` is imported by `VisualStudioEditorDocumentManager`, I've fixed this service as well. |
||
|---|---|---|
| .config | ||
| .github | ||
| .vscode | ||
| docs | ||
| eng | ||
| src | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .vsconfig | ||
| BuildAnalyzers.sln | ||
| CODE-OF-CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| NuGet.config | ||
| README.md | ||
| README_compiler.md | ||
| Razor.Slim.slnf | ||
| Razor.sln | ||
| SECURITY.md | ||
| SpellingExclusions.dic | ||
| activate.ps1 | ||
| activate.sh | ||
| azure-pipelines-compliance.yml | ||
| azure-pipelines-conditional-integration.yml | ||
| azure-pipelines-integration-dartlab.yml | ||
| azure-pipelines-official.yml | ||
| azure-pipelines-richnav.yml | ||
| azure-pipelines.yml | ||
| build.cmd | ||
| build.ps1 | ||
| build.sh | ||
| clean.cmd | ||
| clean.ps1 | ||
| clean.sh | ||
| featurflag.ps1 | ||
| global.json | ||
| restore.cmd | ||
| restore.sh | ||
| startvs.cmd | ||
| startvs.ps1 | ||
README.md
ASP.NET Core Razor
This repository is the open-source implementation for the Razor experience in ASP.NET Core. It contains the compiler and IDE tools for working on Razor ASP.NET Core apps using Visual Studio and Visual Studio Code.
Contributing
All work on Razor 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.
- Check out the contributing page to see the best places to log issues, start discussions, and for general contributing guidelines.
- Instructions to build Razor Tooling source code
- Follow along with the development of ASP.NET Core:
- Community Standup: The community standup is held every week and streamed live to YouTube. You can view past standups in the linked playlist.
Getting Started with Razor
If you are unfamiliar with ASP.NET Core or Razor, follow the links below to learn more:
- ASP.NET Core apps: Follow the Getting Started instructions in the ASP.NET Core docs.
- Razor pages: Visit the tutorial on getting started with Razor pages.
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
Related projects
These are some other repos for related projects:
- ASP.NET Core - the ASP.NET Core framework
- Documentation - documentation sources for https://docs.microsoft.com/aspnet/core/
- Extensions - Logging, configuration, dependency injection, and more.