Blazor in MVC: Component gets rendered, but @onclick not working. Problem with connection
The solution to the problem was changing two things:
- To fix the errors in the console I had to put
<base href="/" />in the header of _Layout.cshtml - To fix the actual @onclick issue I had to put these using statements in the Blazor component:
@using Microsoft.AspNetCore.Components
@using Microsoft.AspNetCore.Components.Web;
After that the @onclick was working and intellisense recognized stuff a bit better in the Blazor component.
From the docs: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/blazor/index?view=aspnetcore-3.0&tabs=visual-studio#app-base-path
App base path
The app base path is the app's root URL path. Consider the following ASP.NET Core app and Blazor sub-app:
- The ASP.NET Core app is named
MyApp:- The app physically resides at d:/MyApp.
- Requests are received at
https://www.contoso.com/{MYAPP RESOURCE}.
- A Blazor app named
CoolAppis a sub-app ofMyApp:- The sub-app physically resides at d:/MyApp/CoolApp.
- Requests are received at
https://www.contoso.com/CoolApp/{COOLAPP RESOURCE}.
Without specifying additional configuration for CoolApp, the sub-app in this scenario has no knowledge of where it resides on the server. For example, the app can't construct correct relative URLs to its resources without knowing that it resides at the relative URL path /CoolApp/.
To provide configuration for the Blazor app's base path of https://www.contoso.com/CoolApp/, the <base> tag's href attribute is set to the relative root path in the Pages/_Host.cshtml file (Blazor Server) or wwwroot/index.html file (Blazor WebAssembly):
<base href="/CoolApp/">
Blazor Server apps additionally set the server-side base path by calling in the app's request pipeline of Startup.Configure:
app.UsePathBase("/CoolApp");
By providing the relative URL path, a component that isn't in the root directory can construct URLs relative to the app's root path. Components at different levels of the directory structure can build links to other resources at locations throughout the app. The app base path is also used to intercept selected hyperlinks where the href target of the link is within the app base path URI space. The Blazor router handles the internal navigation.
In many hosting scenarios, the relative URL path to the app is the root of the app. In these cases, the app's relative URL base path is a forward slash (<base href="/" />), which is the default configuration for a Blazor app. In other hosting scenarios, such as GitHub Pages and IIS sub-apps, the app base path must be set to the server's relative URL path of the app.
To set the app's base path, update the <base> tag within the <head> tag elements of the Pages/_Host.cshtml file (Blazor Server) or wwwroot/index.html file (Blazor WebAssembly). Set the href attribute value to /{RELATIVE URL PATH}/ (the trailing slash is required), where {RELATIVE URL PATH} is the app's full relative URL path.
For an Blazor WebAssembly app with a non-root relative URL path (for example, <base href="/CoolApp/">), the app fails to find its resources when run locally. To overcome this problem during local development and testing, you can supply a path base argument that matches the href value of the <base> tag at runtime. Don't include a trailing slash. To pass the path base argument when running the app locally, execute the dotnet run command from the app's directory with the --pathbase option:
dotnet run --pathbase=/{RELATIVE URL PATH (no trailing slash)}
For a Blazor WebAssembly app with a relative URL path of /CoolApp/ (<base href="/CoolApp/">), the command is:
dotnet run --pathbase=/CoolApp
The Blazor WebAssembly app responds locally at http://localhost:port/CoolApp.