Optionally, components can be added to the NavMenu component so that a link to the component appears in the app's UI-based navigation. In an app created from the Blazor Server project template, the App component (App.razor) is created as the default root component in Pages/_Host.cshtml using the Component Tag Helper: In an app created from the Blazor WebAssembly project template, the App component (App.razor) is created as the default root component in Program.cs: In the preceding code, the CSS selector, #app, indicates that the App component is created for the
in wwwroot/index.html with an id of app: MVC and Razor Pages apps can also use the Component Tag Helper to register statically-rendered Blazor WebAssembly root components: Statically-rendered components can only be added to the app. Generate framework-specific JavaScript (JS) components from Razor components for web frameworks, such as Angular or React. Static assets are located in the project's web root (wwwroot) folder or folders under the wwwroot folder. WCF Dependency Injection using Castle Windsor - Please help? The following Razor syntax is not supported: Component attributes do not support complex content (mixed C# and markup). The following example registers the Counter component with the custom HTML element my-counter: To register a root component as a custom element in a Blazor WebAssembly app, call RegisterCustomElement on RootComponents in Program.cs. Razor Pages handler methods facilitate the clear separation of processing code based on user actions on the page without resorting to a confusing pile of conditional code to determine which button was clicked. etc.. From the list, we can see that these names follow the particular pattern. EventCallback provides enhanced error feedback to users of the component. The default convention works by matching the HTTP verb used for the request to the name of the method, which is prefixed with "On": OnGet (), OnPost (), OnPut () etc. The property Message is displayed with the razor syntax @Model.Message. For more information, see the following resources: Razor components can be dynamically-rendered from JavaScript (JS) for existing JS apps. For guidance on adding packages to .NET apps, see the articles under Install and manage packages at Package consumption workflow (NuGet documentation). The following GenericTypeExample5 component with inferred cascaded types provides the same data for display. Adding an @using directive for the component's namespace makes the component available, which resolves the warning. In JavaScript, define a function for building the custom event argument object from the source event: Register the custom event with the preceding handler in wwwroot/index.html (Blazor WebAssembly) or Pages/_Host.cshtml (Blazor Server) immediately after the Blazor