-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Referencing Microsoft.AspNetCore.Blazor.Server disables server-side tag helpers #15757
Labels
area-blazor
Includes: Blazor, Razor Components
Comments
Aha.. I had to remove the |
@SteveSandersonMS thanks for filing this! @NTaylorMullen - FYI this is the bug I accidentally found on Friday. |
There are two issues here:
We'll need to solve this by making sure that our |
rynowak
referenced
this issue
in dotnet/blazor
Aug 21, 2018
We recommend using this package with PrivateAssets=all everywhere to make sure that the MSBuild files brought in by this package aren't applied to transitively. When that happens, the Blazor.Build MSBuild files will take over the Razor functionality for other projects, which breaks MVC's view compilation functionality. This is part of a fix for #1216.
rynowak
referenced
this issue
in dotnet/blazor
Aug 22, 2018
We recommend using this package with PrivateAssets=all everywhere to make sure that the MSBuild files brought in by this package aren't applied to transitively. When that happens, the Blazor.Build MSBuild files will take over the Razor functionality for other projects, which breaks MVC's view compilation functionality. This is part of a fix for #1216.
Eilon
referenced
this issue
in Eilon/Hubbup
Aug 28, 2018
To avoid this issue: https://github.com/aspnet/Blazor/issues/1216
Eilon
referenced
this issue
in Eilon/Hubbup
Aug 28, 2018
Done |
SteveSandersonMS
referenced
this issue
in SteveSandersonMS/BlazorMigration
Nov 27, 2018
We recommend using this package with PrivateAssets=all everywhere to make sure that the MSBuild files brought in by this package aren't applied to transitively. When that happens, the Blazor.Build MSBuild files will take over the Razor functionality for other projects, which breaks MVC's view compilation functionality. This is part of a fix for #1216.
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Repro:
AddMvc
if not already present, then putIndex.cshtml
into aPages
directory)@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
if you don't have it in_ViewImports.cshtml
already<img src="~/blah.jpg" />
, it does not resolve the~
- it literally emits the URL~/blah.jpg
I expect that Blazor's MSBuild targets are hijacking the server-side Razor compilation process, eliminating the normal server-side tag helpers, or something of that sort.
The text was updated successfully, but these errors were encountered: