Instead, they become part of what is called
a satellite assembly, which contains just the localized resources as part of its content. It does
this in an organized fashion using a specific file folder structure so the ResourceManager class
can find it. For the two preceding files, LocalStrings.en-MX.resx and LocalStrings.de.resx
are located in the folder structure shown in Figure 13-14.
The ResourceManager resource resolution process first attempts to take an exact match if it
is provided with a specific culture. An example of this type of specific culture string is ???es-MX???.
In this case, there is a matching satellite assembly, so ResourceManager will pull the localized
text from it.
The globalization support has a fallback mechanism in the event that an exact match
cannot be found, as shown in Figure 13-15. If the fallback process cannot find an exact match,
it continues until it either finds a suitable neutral culture match or winds up with the invariant
culture in the main assembly. For example, if we specify a culture string of ???fr-FR??? for French
spoken in France, we would end up with the English string from the main assembly, because
we do not have a satellite assembly for the French language.
CHAPTER 13 ?– P ACKAGI NG AND DEPLOYMENT 703
Figure 13-14.
Pages:
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897