[Blazor] Suggestions for improved VS editing experience

[daniel-p-tech]

Hello team,

I suspect many developers using Blazor come from WPF/WebForms environment and prefer clean separation of UI markup and C# code. VS currently supports rather cumbersome way of creating CompnentXYZ.razor.cs file (without partial keyword that still needs to be supplied manually). I would like to suggest implementation of "View Code" context menu in both Razor editor and Solution Explorer (just like in WebForms) that would switch to CompnentXYZ.razor.cs file or create one if it does not exist. Now that CSS/JS isolation is being developed, this concept can be expanded to "View CSS" and "View JS" context menu option as well.

Second suggestion is to implement a VS tool to reformat Razor code (again something similar to WebForms). I find myself often breaking the layout of Razor code by making small changes (creating new nested components etc) and to my knowledge there is no automated way to fix the formatting.

Thanks!

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[NTaylorMullen]

Hi @daniel-p-tech, in latest VS2022 builds we've brought forward the ability to "View Code" for C# files (wont create one if it's not already there); however, creating CSS/JS doesn't exist quite yet. Interesting idea though! I'll leave this open for more folks to share their feedback.

[daniel-p-tech]

This is great news, thanks for letting me know!

[daniel-p-tech]

@NTaylorMullen the "View Code" menu item seems to be missing when I create a new razor file. If I open a razor file that already has "XYZ.razor.cs" file then the option is available. I'm running VS 17.0.0.

Thanks.

[danroth27]

You can now extract code blocks from .razor files to a code-behind file using a quick action.

You can also navigate between the code-behind and the original Razor file using the F7 keyboard shortcut, although we don't provide a context menu item for this or for navigating to .razor.css or .razor.js files.

VS does support formatting .razor files using the normal format document gesture.

Since this issue is currently tracking multiple feature requests, I'm going to close it and break the remaining items out into separate issues so they can be independently triaged and voted on (👍) by the community.