SDK does not correctly resolve RazorExtension when multiple instances of RazorConfiguration are present
pranavkm opened this issue · 0 comments
pranavkm commented
This is a bug in how we do filtering here: https://github.com/aspnet/Razor/blob/master/src/Microsoft.NET.Sdk.Razor/build/netstandard2.0/Sdk.Razor.CurrentVersion.targets#L282-L284
In addition, there's also an issue when multiple instances of RazorConfiguration with the same identity are resolved. This occurs in our interim builds when projects target netcoreapp3.0 but resolve a Microsoft.AspNetCore.App v2.x. We can do a small fix to do a better job here.