Sign in to follow this  

[.net] file hierarchy and .net expectations

This topic is 3743 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

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.resources However 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?

Share this post


Link to post
Share on other sites

This topic is 3743 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this