Skip to content

Fix custom Razor commands for cohosting #8251

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

Merged
merged 2 commits into from
May 6, 2025

Conversation

davidwengier
Copy link
Member

Fixes dotnet/razor#11785

Makes the "Report Razor issue" command work with cohosting, and hides the "Show Razor C#" command (not possible in cohosting) and "Show Razor Html" command (I'm lazy and I don't think it has any value).

The "Report issue" command still gets the Html content, for whatever its worth.

@davidwengier davidwengier requested review from a team as code owners May 6, 2025 04:15
@davidwengier davidwengier merged commit 6b0da5b into dotnet:main May 6, 2025
24 checks passed
@davidwengier davidwengier deleted the RazorCommands branch May 6, 2025 06:26
@dibarbet
Copy link
Member

dibarbet commented May 6, 2025

"Show Razor C#" command (not possible in cohosting)

Is it possible to go to the source generated razor file using the normal source generator opening support we have?

@davidwengier
Copy link
Member Author

Yeah, I'm sure that would work too. When I say "not possible", I really mean "not possible now". If we reuse the existing generated document provider, we'd probably need to go to the server to find out the filename/documentId, but if we're going to the server we could also just get the contents of the file :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[VS Code] [Cohosting] Custom commands don't work
4 participants