Application localization (culture) DLLs
-
Hi. I noticed that when creating a localized application (by separating languages in interface) compiler creates subfolders for those languages and places the DLLs in them. I am trying to find a way to implement these DLLs in the Application assembly and avoid the need of subfolders for these DLLs, Please advice. Thanks.
-
Hi. I noticed that when creating a localized application (by separating languages in interface) compiler creates subfolders for those languages and places the DLLs in them. I am trying to find a way to implement these DLLs in the Application assembly and avoid the need of subfolders for these DLLs, Please advice. Thanks.
The reason that it places them in subfolders is so that the runtime can pick the relevant one up - basically, the name of the folder follows a special naming convention which allows the localisation code to pick up a specific culture if it's available, drop back to the language if it's not, and then fall back to the default language if that's not available. Trying to circumvent this means that you will have to code the infrastructure yourself. What business reason do you have for wanting to do this?
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
The reason that it places them in subfolders is so that the runtime can pick the relevant one up - basically, the name of the folder follows a special naming convention which allows the localisation code to pick up a specific culture if it's available, drop back to the language if it's not, and then fall back to the default language if that's not available. Trying to circumvent this means that you will have to code the infrastructure yourself. What business reason do you have for wanting to do this?
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Thanks pete. I Realize that. I just wonder if there is a way to implement it in one assembly.