Skip to content

Blazor server SignalR disconnects when a component is included in both a razor page and a layout page #14474

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.

Sign up for GitHub

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

Jump to bottom
Closed
ACertainDeveloper opened this issue Sep 26, 2019 · 2 comments
Closed

Blazor server SignalR disconnects when a component is included in both a razor page and a layout page #14474

ACertainDeveloper opened this issue Sep 26, 2019 · 2 comments
Assignees
@pranavkm
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed
Milestone
3.1.0-preview2

Comments

@ACertainDeveloper
Copy link

Describe the bug

Blazor server SignalR disconnects when a component is included in both a razor page and a layout page.

To Reproduce

Steps to reproduce the behavior:

  1. Using this version of ASP.NET Core '3.0'
  2. Create a new asp.net core web application
  3. Add blazor.server.js to layout page.
  4. Add MapBlazorHub() and AddServerSideBlazor() to Startup
  5. Add a component to both the layout page and a razor page

Expected behavior

Blazor components rendered on razor pages should function normally when a component is included in the layout.

Example App

Example App
@ACertainDeveloper
Copy link
Author

Screenshot of error

@mkArtakMSFT mkArtakMSFT added the area-blazor Includes: Blazor, Razor Components label Sep 26, 2019
@mkArtakMSFT
Copy link
Contributor

Thanks for contacting us, @ACertainDeveloper.
@pranavkm can you please look into this? Thanks!

@pranavkm pranavkm mentioned this issue Oct 14, 2019
Closed
pranavkm added a commit that referenced this issue Oct 14, 2019
@pranavkm
Account for Layout ordering in Blazor
9cfe081 
The server requires that clients send descriptors in sequence. Since MVC executes
Layouts in an inside-out manner, modify the client to explicitly order descriptors

Fixes #14474
@pranavkm pranavkm mentioned this issue Oct 14, 2019
Merged
@pranavkm pranavkm added bug This issue describes a behavior which is not expected - a bug. and removed investigate labels Oct 14, 2019
pranavkm added a commit that referenced this issue Oct 15, 2019
@pranavkm
Account for Layout ordering in Blazor (#15001)
30b31d7 
The server requires that clients send descriptors in sequence. Since MVC executes
Layouts in an inside-out manner, modify the client to explicitly order descriptors

Fixes #14474
@pranavkm pranavkm added the Done This issue has been fixed label Oct 15, 2019
@ccit-spence ccit-spence mentioned this issue Nov 8, 2019
Closed
@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2019
3dots pushed a commit to 3dots/aspnetcore-Web.JS that referenced this issue Feb 19, 2024
@pranavkm
Account for Layout ordering in Blazor (#15001)
25aa01c 
The server requires that clients send descriptors in sequence. Since MVC executes
Layouts in an inside-out manner, modify the client to explicitly order descriptors

Fixes dotnet/aspnetcore#14474
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pranavkm pranavkm

Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed
Projects
None yet
Milestone
3.1.0-preview2
Development

No branches or pull requests
3 participants
@pranavkm @mkArtakMSFT @ACertainDeveloper