As part of our ongoing work to improve the Razor experience, both compiler and tooling, we’re planning to make dotnet/roslyn the new source of truth for Razor development. That means we intend to mono-repo Razor into Roslyn, and over time retire this repository as the primary home for the Razor compiler and tooling code.
In practical terms:
- Code will move to Roslyn. Development in the
main branch will happen there as soon as the move takes place. This repo will transition to a legacy role for servicing release/insiders and release/stable at whichever versions they represent at the time of the move. Eventually the repo will become read-only, and most likely archived, once those versions leave servicing.
- Issues will consolidate. We expect to migrate some (or possibly most) open issues to Roslyn so discussion and tracking can happen in one place. With all of the large changes that Razor has undergone with cohosting, we will use this opportunity to clean the backlog and so we won't transfer every issue as-is.
- Open PRs will need to be re-opened in the Roslyn repo after the move. We will maintain history on all of the existing files, and we're working on scripts to do this move in the most git-friendly way, so replaying your commits should be as painless as possible, but there may be some turmoil.
The goal of the move is to reduce duplication, improve coordination with Roslyn, and make it easier for the team (and contributors!) to work in a single, well-supported place.
UPDATE September 2026: All shipping code is in the Roslyn repo, all open issues are in the Roslyn repo. You should probably be looking at the Roslyn repo right now :)
As part of our ongoing work to improve the Razor experience, both compiler and tooling, we’re planning to make dotnet/roslyn the new source of truth for Razor development. That means we intend to mono-repo Razor into Roslyn, and over time retire this repository as the primary home for the Razor compiler and tooling code.
In practical terms:
mainbranch will happen there as soon as the move takes place. This repo will transition to a legacy role for servicingrelease/insidersandrelease/stableat whichever versions they represent at the time of the move. Eventually the repo will become read-only, and most likely archived, once those versions leave servicing.The goal of the move is to reduce duplication, improve coordination with Roslyn, and make it easier for the team (and contributors!) to work in a single, well-supported place.
UPDATE September 2026: All shipping code is in the Roslyn repo, all open issues are in the Roslyn repo. You should probably be looking at the Roslyn repo right now :)