Skip to content

What is the purpose of themes in multi tenancy if modules can't link to static files? #10595

Answered by Skrypt
inzi asked this question in Q&A
Discussion options

You must be logged in to vote

What's the point of themes? Do we have to do a resource for everything? one image is not a problem, but what about a professional theme which may hundreds of images?

Static assets from a module are always resolved with an assembly path. Here, each module or theme is equivalent to an MVC Area. So, unless you put your assets in a wwwroot folder of that module or theme, static assets are always embedded inside the assembly, this is why you resolve their path with the module or theme name. As you said, that's all standard ASP.NET MVC.

This is all standard dotnet - but if every theme ThemeA and ThemeB BOTH was to map "/images" to THEIR wwwroot, this is a problem. The first to map will get i…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@inzi
Comment options

Answer selected by inzi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants