Always use the Razor source generator in design time builds if cohosting is enabled #12240
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Alternatively, we could won't fix this: Lets see if the test insertion shows up any issues: https://dev.azure.com/devdiv/DevDiv/_git/VS/pullrequest/671375 |
DustinCampbell
approved these changes
Sep 18, 2025
|
Test insertion was all green ✅ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also sets a global property to tell us if cohosting is enabled, which might come in handy later.
This fixes opening .NET Standard, or .NET Core <= 5, targeted Razor projects in VS. VS Code will need more work, and its more painful, so I don't think its worth fixing that without user feedback. The only reason to use .NET Standard is if you're multi-targeting with .NET Framework (ASP.NET Core 2.x), and those projects don't work in VS Code anyway, so seems unlikely. Multi-targeting fixes the issue, and at worst it falls back to a Misc Files experience, so no errors or anything horrible.