Examples on how to affect the Layout rendering from Body component

[RichiCoder1]

It's not clear if it's possible to pass data from the wrapped component to the Layout ala https://docs.microsoft.com/en-us/aspnet/web-pages/overview/ui-layouts-and-themes/3-creating-a-consistent-look#passing-data-to-layout-pages, and if so how. Clarification would be great

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cce76032-e7b4-d168-6e24-c2cb88ae7e44
• Version Independent ID: f3ecd255-c3ce-9162-ddf1-67b35aeffc11
• Content: Razor Components layouts
• Content Source: aspnetcore/razor-components/layouts.md
• Product: aspnet-core
• GitHub Login: @guardrex
• Microsoft Alias: riande

[guardrex]

Might be a dup or related to #11243.

[guardrex]

I'll be working on #11243 tomorrow (Wednesday, 4/3). @RichiCoder1, I'm going to move this to a comment on that issue as a reminder to test the EventCallback/chained binding bits with a layout to confirm it works. Even if it doesn't work as expected (and I doubt that will be the case), I'll note that it doesn't work with layouts in the PR tomorrow. Thanks for opening this ... you can track it on #11243.

[guardrex]

We discussed this: We have coverage enhancements to make for this scenario: A useful approach is using a service (DI) to communicate across the component-layer barrier. We'll document that approach.

[guardrex]

@RichiCoder1 Engineering is going to address it formally. dotnet/aspnetcore#10131

[RichiCoder1]

Sounds good! The referenced issue is basically exactly what I was looking for.

[guardrex]

@RichiCoder1 Yes, was happy to hear from DR that they're working on a framework scenario for it. At least in the short-term until they get there (this preview) , the approach offered by @sven5 is pretty sweet. That should at least tide everyone over. We'll get the bits that they build into the docs ASAP after release.