   [.net] file hierarchy and .net expectations
  I am currently writing a piece of software composed of several assemblies, some of which makes the core functionality and some are independant module. Also each assembly is localized in different languages. I wish at the end to organise the files in a way like this :Application Directory| * Application.exe+ Core|  * SomeCoreAssembly.dll|  * SomeCoreAssembly2.dll+ Modules|  * ModuleAssembly.dll+ Languages  + English  |  * SomeCoreAssembly.en.resources  |  * SomeCoreAssembly2.en.resources   + Français  |  * SomeCoreAssembly.fr.resources  |  * SomeCoreAssembly2.fr.resourcesHowever this is not how the framework expects the files to be ordered. Localization fallback no longer work and i had to write my own resources manager. Assembly resolve has to be done "by hand" in AssemblyResolveEvent... At first it didnt looked like it was a big problem but as the number of files starts to grow, i feel that i may not be going in the right direction.So how do you organize your assemblies in the end? Do you stay with .net expectations or do you keep your own hierarchical structure and try to adapt the framework?   
  If I'm loading assemblies at runtime, I put the assemblies wherever I want and use a configuration file to specify the path to the assemblies I want to load with a custom loader.   