Does it make no sense to have a external resource dll in ASP MVC?

Question

I have been trying to find recommended practices for resource management in the ASP.NET MVC app.. (target .NET 4.0 )

so far I have not been able to figure out whether should I add a separate satellite assembly to my MVC app or add the resources in the project itself.

Also the satellite assembly creation is quite different in MVC Apps. Perhaps they are not even called as satellite assemblies.. What I understood is that in order to refer to an external resource.dll file, I should create a different ASP.NET MVC prjoect, add my resource files to the "Resources" folder and then add references to the dlls thus generated. Is this the correct way? The al.exe process is I believe not relevant for MVC apps.

Answer 1

I bundled these resources in a separate dll as per Mark and this seems to work fine..