{"id":55550,"date":"2025-02-13T10:05:00","date_gmt":"2025-02-13T18:05:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=55550"},"modified":"2025-02-18T15:56:14","modified_gmt":"2025-02-18T23:56:14","slug":"enhancing-razor-productivity-with-new-features","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/enhancing-razor-productivity-with-new-features\/","title":{"rendered":"New Features for Enhanced Razor Productivity!"},"content":{"rendered":"

If you are building web apps with Razor, we have some great new features that you are going to love for both Visual Studio and Visual Studio Code! Extract to Component refactoring and the new Roslyn-based C# tokenizer are now available and are designed to improve your productivity in Razor files, let’s take a look.<\/p>\n

Extract to Component<\/h2>\n

Extract to Component, available in Visual Studio 17.12, is a new refactoring that automates the process of creating a new Razor\/Blazor component. Instead of manually creating a new file and copy\/pasting the code you want to extract, selecting this feature will do that work for you by selecting the lightbulb refactoring (CTRL + .<\/code>) after highlighting the code (or tag) you want to extract. This feature makes it easier to create reusable components, allowing for a cleaner and more manageable codebase.<\/p>\n

\"Figure<\/p>\n

\"Figure<\/p>\n

In this first iteration of the feature, Extract to Component focuses on support for basic, mostly HTML-based extraction scenarios. However, we have plans to add additional improvements and more advanced scenarios (i.e. more consistent extractions involving variable dependencies, C#, parameters, etc.).<\/p>\n

Roslyn C# Tokenizer<\/h2>\n

The C# tokenizer \/ lexer update brings significant improvements to how Razor handles C# code. Many users have expressed frustrations with not being able to use raw string literals and verbatim interpolated strings in Razor files, and the new Roslyn C# lexer fixes that! In addition to these string formats, the lexer also adds support for binary literals and improves the handling of C# preprocessor directives, ensuring they follow C# rules. Ultimately, the new lexer will also make it easier to support new C# language features going forward.<\/p>\n

\"Figure<\/p>\n

\"Image<\/a><\/p>\n

This new tokenizer is not on by default until .NET 10 but is available in both Visual Studio (17.13) and Visual Studio Code for .NET 9. To enable the C# tokenizer today, check the Use the C# tokenizer for Razor files in the IDE<\/strong> option under Tools > Options > Preview Features<\/strong> and add <Features>use-roslyn-tokenizer;$(Features)<\/Features><\/code> to a property group in your .csproj<\/code> or directory.props<\/code> file:<\/p>\n

\"Image<\/a><\/p>\n

This new lexer does currently come with some breaking changes, particularly around preprocessor directives, so we encourage you to please share any related issues you may experience in the Razor Github repository<\/a>.<\/p>\n

Summary<\/h2>\n

These two updates, Extract to Component and the C# tokenizer, help enhance your Razor productivity. By adopting these features, you can ensure cleaner code, better language support, and an overall more efficient development process. However, there\u2019s always room for improvement! To share your Razor feedback, submit issues in our Razor Github repo<\/a>, the Developer Community<\/a>, or check out this survey<\/a> to share your Extract to Component feedback!<\/p>\n

Finally, if you\u2019d like to chat directly with the Razor team about our upcoming roadmap and how we\u2019re addressing your issues, you can join our upcoming .NET Community Standup<\/a> on February 18th!<\/p>\n","protected":false},"excerpt":{"rendered":"

The Extract to Component refactoring and the Roslyn tokenizer are two new features designed to help improve your productivity in Razor files.<\/p>\n","protected":false},"author":651,"featured_media":55551,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[685,7509,7251,646,7593],"tags":[7205,7384],"class_list":["post-55550","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet","category-aspnetcore","category-blazor","category-visual-studio","category-visual-studio-code","tag-blazor","tag-razor"],"acf":[],"blog_post_summary":"

The Extract to Component refactoring and the Roslyn tokenizer are two new features designed to help improve your productivity in Razor files.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/55550","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/651"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=55550"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/55550\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/55551"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=55550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=55550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=55550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}