You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: knowledge-base/notification-single-app-instance.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,11 @@ There are two possible ways to implement a reusable Notification component insta
34
34
*[Pass the Notification in a Cascading Value](#pass-the-notification-in-a-cascading-value)
35
35
*[Use the Notification as a Service](#use-the-notification-as-a-service)
36
36
37
+
The Notification component in both scenarios must be defined:
38
+
39
+
1. As a descendant (or child) of the [`<TelerikRootComponent>`]({%slug rootcomponent-overview%}).
40
+
1. In a `.razor` file with enabled interactive render mode. The `MainLayout` is interactive only if the Blazor app has **Global** interactivity location.
41
+
37
42
### Pass the Notification in a Cascading Value
38
43
39
44
1.[Define a Telerik Notification component]({%slug notification-overview%}#creating-blazor-notification) in `MainLayout.razor`.
0 commit comments