Allow Razor cohosting to work with non-Razor SDK projects#8559
Allow Razor cohosting to work with non-Razor SDK projects#8559davidwengier merged 6 commits intodotnet:mainfrom
Conversation
| // Razor has code in Microsoft.CSharp.DesignTime.targets to handle non-Razor-SDK projects, but that doesn't get imported outside | ||
| // of DevKit so we polyfill with a mini-version that Razor provides for that scenario. |
There was a problem hiding this comment.
Why aren't we importing the same support directly?
There was a problem hiding this comment.
In DevKit the targets file comes from the Microsoft.VisualStudio.ProjectSystem.Managed package which we don't reference in the C# extension. Seemed like a large hammer for one xml file. We'd still need all of the changes in this PR anyway, to pass the path through to msbuild etc. it would just be path itself that would change.
There was a problem hiding this comment.
I presume we also need this for C# standalone scenarios, when devkit isn't available?
There was a problem hiding this comment.
Yeah, thats the only scenario this code runs in. With DevKit, we leave it up to it.
|
Bumped Razor and Roslyn, so this should build now (and work!) |
Co-authored-by: Joey Robichaud <joseph.robichaud@microsoft.com>
Fixes dotnet/razor#11834
Razor bump to 10.0.0-preview.25424.9:
View Complete Diff of Changes
Roslyn bump to 5.0.0-2.25424.1:
View Complete Diff of Changes
usingdirectives (PR: #79890)initaccessor for required properties insidereadonly structs (PR: #80004)SymbolDisplay.FormatPrimitive(PR: #79869)