How dotnet know where _Imports.razor is?
When creating Blazor project with dotnet new blazor _Imports.razor get created in Components directory. It's working fine.
I've server-side Blazor project "mutated" gradually from .NET Core 3.x to .NET 8 mostly by using upgrade-assistant command. _Imports.razor is in the root directory of project and it's also working fine. I want to try to "modernize" this project structure to something resembling dotnet new blazor template.
I tried moving even just _Imports.razor to Components directory (in Program.cs I've added using Project.Components;) but this operation breaks whole application horribly (a lot of unknown namespaces).
What further puzzles me is that I can move _Imports.razor to root directory in new Blazor project and it's still working fine. How this is possible? What determines where _Imports.razor can be and where not?
We have a section which containing description like below:
Every folder of an app can optionally contain a template file named _Imports.razor. The compiler includes the directives specified in the imports file in all of the Razor templates in the same folder and recursively in all of its subfolders. Therefore, an _Imports.razor file containing @layout DoctorWhoLayout ensures that all of the components in a folder use the DoctorWhoLayout component. There's no need to repeatedly add @layout DoctorWhoLayout to all of the Razor components (.razor) within the folder and subfolders.
In other words, .net will check each folder to get the _Imports.razor in blazor project to make sure all the components in a folder could reuse the reference. I had a test in my side, which using a component defined in RCL in my main blazor server application. We know that it requires to write like <ComponentLibrary.Component1 /> or @using ComponentLibrary <Component1 />.
If we put @using ComponentLibrary in the root _Imports.razor, we can still write <Component1 />. The same if we create a sub _Imports in Pages folder. But if I create another component which is put under the root folder, only the configuration in root _Imports could make it work.
===========================
Deleting the root _Import.razor
- Dependency Injection on AuthorizationOptions Requirement in DotNet Core
- Enable OPTIONS header for CORS on .NET Core Web API
- ASP.NET Core 8 OpenID Connect - SUB claim missing on User.Identity
- Pager in .Net Core 2.1
- What is different in my Ajax vs XMLHttpRequest Call that lets my Server understand Ajax but not XMLHttpRequest?
- Enable interactive render mode on Blazor templates accounts pages
- .Net Core SignalR Connection between services has an issue
- How to register multiple implementations of the same interface with different dependencies
- ASP.NET Core hosting environment variable ignored
- How to get return value from Task wait()
- User.Identity.IsAuthenticated always false in .net core custom authentication
- I want to pre-fill an input of type IFormFile
- Net Core Simple way to Find Temperature from Openweather API
- Get email claim from identity after upgrading to .NET 8 not working
- Unable to send the List of model data to a view using asp.net mvc
- Routing with Areas and Controller Name (asp.net core)
- Bind gRPC services to specific port in aspnetcore
- Redis cache in .NET 8 is not taking effect?
- Use React Authentication with .NET backend?
- List users with roles in a razor page using asp.net 6.0 Identity
- Correct handling of formless AJAX POST and AntiForgery in C# Razor Pages
- how to load partial view in ajax in asp.net core
- Entity Framework Core multiple connection strings on same DBContext?
- error A value of type 'int' cannot be used as a default parameter because there are no standard conversions to type
- What is this string inside Blazor components HTML tag
- Blazor Server: Breadcrumb change using JavaScript persists across pages
- .net blazor new debug profile lacks .css .js why?
- How to get results from a Postgresql function using EF Core?
- ASP Net identity two factor authentication last expired token is getting validated successfully
- Why string property must be declared as nullable string in Entity Framework Core when corresponding database table column is nullable