Hello everyone. I wanted to let you know that Razor cohosting is now enabled in Visual Studio 2026 18.3 (released yesterday). With cohosting, the Razor language service no longer runs as a separate external process; it now runs alongside Roslyn within the same process. This should significantly improve performance and reliability of the Razor editor as well as .NET Hot Reload.
If you are editing Razor files regularly, we recommend upgrading to the latest version of Visual Studio 2026 to get these benefits, here is the download link https://visualstudio.microsoft.com/downloads/. Once you have a chance to try it, please let us know of any issues that you run into by filing new issues in this repository. If you've had issues with Razor in the past, please try those scenarios in this new version to see if they still exist. This update will broadly impact Razor and invalidate many of the issues which have been reported in the past.
The Legacy Razor Editor for ASP.NET Core has been fully replaced by the modern Razor editor running in cohosting mode. The legacy editor is no longer available.
The option in Tools > Options to enable the Legacy Razor Editor is no longer used and will be removed in a future version of Visual Studio.
Hello everyone. I wanted to let you know that Razor cohosting is now enabled in Visual Studio 2026 18.3 (released yesterday). With cohosting, the Razor language service no longer runs as a separate external process; it now runs alongside Roslyn within the same process. This should significantly improve performance and reliability of the Razor editor as well as .NET Hot Reload.
If you are editing Razor files regularly, we recommend upgrading to the latest version of Visual Studio 2026 to get these benefits, here is the download link https://visualstudio.microsoft.com/downloads/. Once you have a chance to try it, please let us know of any issues that you run into by filing new issues in this repository. If you've had issues with Razor in the past, please try those scenarios in this new version to see if they still exist. This update will broadly impact Razor and invalidate many of the issues which have been reported in the past.
The Legacy Razor Editor for ASP.NET Core has been fully replaced by the modern Razor editor running in cohosting mode. The legacy editor is no longer available.
The option in Tools > Options to enable the Legacy Razor Editor is no longer used and will be removed in a future version of Visual Studio.