Damian,

It looks like you are on the right track.

For getting the resources to work you could do:

module.LocalResourceFile = this.LocalResourceFile;

which would assign the resource of the module you are currently working with to the module you are trying to load. However that might not be exactly what you want to do. Say if your container module does not have the necessary string resources to service the "~/DesktopModules/Comentarios/View.ascx" module then you might want to do something like:

module.LocalResourceFile = "~/DesktopModules/Comentarios/App_LocalResources/View.ascx"; 

Assuming there is an actual file "~/DesktopModules/Comentarios/App_LocalResources/View.ascx.resx".

Now why the external module is not loading its data correctly is a little bit of an open issue. It depends on how that module actually works. One potential problem could be that you are assigning the module configuration from the container module to the external module with this statement:

module.ModuleConfiguration = ModuleConfiguration;

This means that the external module would now load all settings using the container module id. If the external module has its own configuration/settings for its internal functioning it might not be able to work with the configuration of the container module. If you tell me a little bit more about what you are trying to achieve maybe I could give more advice.

Here is how you could load an external module's configuration, but you need the module and tab ids.

ModuleController moduleController = new ModuleController();
        ModuleInfo externalModuleConfiguration = moduleController.GetModule(moduleID, tabID, ignoreCache);
        module.ModuleConfiguration = externalModuleConfiguration;