Skip to content
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

Question: Razor Language Server Protocol (LSP) for MVC 5 #5131

Closed
tompazourek opened this issue Sep 30, 2020 · 4 comments
Closed

Question: Razor Language Server Protocol (LSP) for MVC 5 #5131

tompazourek opened this issue Sep 30, 2020 · 4 comments
Assignees

Comments

@tompazourek
Copy link

Just read about the New experimental Razor editor for Visual Studio.

Will this new Razor editor support editing of the ASP.NET MVC 5 Razor, or is it strictly for the new ASP.NET Core Razor?

If it did, it might be a way to resolve Razor Intellisense issues with MVC 5 projects using the new SDK-style project system (see dotnet/project-system#2670 (comment)). I'm just curious.

Thanks for the information, I'm glad to learn more about this cool feature.

@NTaylorMullen NTaylorMullen self-assigned this Oct 5, 2020
@NTaylorMullen
Copy link
Contributor

Hi @tompazourek I'm glad you're as excited about this new effort as we are! The first iterations of the experimental Razor editor will not support the pre-existing ASP.NET MVC 5 Razor skew; however, it is something we may re-evaluate in the future 😄

@tompazourek
Copy link
Author

@NTaylorMullen Thanks, good to know.

@CZEMacLeod
Copy link

@NTaylorMullen Just a quick note to say that this would be a major boost for those still having to handle legacy applications and frameworks. Using the RazorGenerator.MsBuild package in an SDK style project produces class libraries with UI that can be much more easily edited and managed etc. with just a bare-bones legacy ASPNET5 project in the old format but editing Razor files is the major hurdle for maintenance.
I understand that most effort will have to go into supporting new tech, but this would really help enable editing, maintaining and migrating legacy code.

@tompazourek
Copy link
Author

@CZEMacLeod I agree, as noted in my comment dotnet/project-system#2670 (comment), Rider actually doesn't have the Intellisense issues as VS on older ASP.NET MVC 5 projects so maybe Rider is the way to go for legacy apps.

@ghost ghost locked as resolved and limited conversation to collaborators Nov 13, 2020
@ghost ghost unlocked this conversation Oct 8, 2021
@allisonchou allisonchou transferred this issue from dotnet/aspnetcore Oct 8, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Nov 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants