-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for .razor files #4468
Comments
The only place I'm aware of in the project-system that special cases Line 19 in 6aa3664
From the point of view of the project-system this should be the same - it will be ItemGroup |
Tagging @jjmew as well |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ASP.NET Core 3.0 adds support for Razor Components, a new way to write client-side web UI. Razor Component files are Razor files (like .cshtml files) that get compiled to .NET classes that render to a structured presentation of the DOM. This allows the runtime to efficiently figure out exactly which parts of the DOM need to be updated. Because Razor Components use a fundamentally different compilation model from MVC views/pages they will have a different file extension: .razor.
Broadly speaking we need all our partner teams that special case .cshtml files today to also support .razor files. In .razor files you should get a rich C# editing experience and rich debugging experience in both web and class libraries just like you do with .cshtml files today. We want to land this work to support .razor files in the first update preview of VS2019 so that folks can start trying it out with the new Razor Component support in .NET Core 3.0.
@cartermp @rynowak
The text was updated successfully, but these errors were encountered: