-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Blazor Component Embedded in Razor Page #9834
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
Comments
I can replicate this scenario in any standard MVC or Razor Page default template. Link to a page with a Blazor component and all of the other page links will no longer function. You can even replicate the same situation using the boilerplate template app for a Blazor Server Side app and linking to any mvc view or razor page. All links no longer work. This has to be a Startup issue. Removing |
MVC Repo with same issue - https://github.com/CarrotSolutions/Blazor12MvcWebApp.git |
I can also replicate this. I guess it has something to do with the client-side router, probably hijacking the url changes and trying to resolve them to components. |
Exactly, The capability of being able to use Blazor components inside of existing Razor or MVC apps is where this tech will gain traction in the beginning . Note, I also tried mapping the razor pages inside Startup, verifying all pages has unique routes, etc. Nothing works. |
I also replicated this using razor pages. |
* Defer link interception until Router is initialized Fixes #9834
Just curious, when an issue like this is CLOSED, does it mean that if I download the latest master, should it be fixed? Thanks |
@chrdlx Yes, but potentially with some latency as it takes some time for all the ASP.NET Core bits to make their way into the .NET Core SDK builds: https://github.com/aspnet/AspNetCore/blob/master/docs/DailyBuilds.md |
Repo: https://github.com/CarrotSolutions/WebApplication1.git
Please Help! We created a basic template razor page app. We added Blazor components. We have no problem getting this to work via replicating the steps in the 04/16 Blazor Update video or using the Blazor documentation. However, once we add the Blazor component to a Razor page, all of our asp-page links no longer work. The url changes in the address bar, but we remain on the same page. The startup file is as follows:
Page with working Component and broken link
The text was updated successfully, but these errors were encountered: