How does .NET5 embed static files in DLLs, and how to use the files embedded in DLLs with the host program?
TinyVFS is a virtual file system, inspired by the ABP vNext framework. It can embed js, CSS, image, cshtml, and other files into the assembly, and they can be used like physical files at runtime.
Features
- In a single application, it can divide the front end and back end (management system) into separate projects.
- It allows developers to develop different businesses or modules at the same time.
- It allows us to split the system function modules and assemble them.
Quick Start
Install-Package
Install-Package TinyVFS
Registering Embedded Files
Edit web resource project .csproj
- <ItemGroup>
- <EmbeddedResource Include="MyResources\**\*.*" />
- <Content Remove="MyResources\**\*.*" />
- </ItemGroup>
Embed the file into the virtual file system with the following code snippet,
- services.AddVirtualFilesService();
- services.Configure < VirtualFileSystemOptions > (options => {
- options.FileSets.AddEmbedded < WebApplication1.Pages.IndexModel > ("WebResources");
- });
Getting Virtual Files: IVirtualFileProvider
After embedding into the assembly, you can obtain the file or directory content through IVirtualFileProvider
- public class MyService {
- private readonly IVirtualFileProvider _virtualFileProvider;
- public MyService(IVirtualFileProvider virtualFileProvider) {
- _virtualFileProvider = virtualFileProvider;
- }
- public void Foo() {
-
- var file = _virtualFileProvider.GetFileInfo("/MyResources/js/test.js");
- var fileContent = file.ReadAsString();
-
- var directoryContents = _virtualFileProvider.GetDirectoryContents("/MyResources/js");
- }
- }
Dynamic listening file
When we are developing on the local machine, maybe we will modify the static files in the resource project, so the normal operation can let us regenerate the code.
Now we can use ReplaceEmbeddedByPhysical to refresh through the browser to get the latest file information,
- services.AddVirtualFilesService();
- services.Configure < VirtualFileSystemOptions > (options => {
- options.FileSets.ReplaceEmbeddedByPhysical < WebApplication1.Pages.IndexModel > (Path.Combine(WebHostEnvironment.ContentRootPath, "..\\WebResources"));
- });
Virtual Files Middleware
Virtual file middleware is used to provide embedded (js, CSS, image …) files to the client/browser, just like the physical (static) file in the wwwroot folder. Add it after the static file middleware, as shown below,
If you want to extend other file formats, you can use the overloaded method, as shown below,
- var provider = new FileExtensionContentTypeProvider();
- provider.Mappings[".less"] = "text/css";
- app.UseVirtualFiles(provider);
By setting the virtual file middleware, it is possible to place the physical file in the same position as the virtual file, thereby making it possible for the physical file to cover the virtual file.
ASP.NET Core Integration
Virtual files can be integrated directly into ASP.NET Core,
- Virtual files can be used like physical static files in web applications.
- Razor Views, Razor Pages, js, CSS, image files, and all other web content can be embedded in the assembly and used like physical files.
- The application can overwrite the virtual file of the module (web resource), just like putting a file with the same name and extension into the same folder of the virtual file.
Views & Pages
They do not require any configuration and can be used in our applications. When these files exist in our physical directory, they overwrite the virtual files.