asp.net - .NET Localization Satellite Assemblies -
we have website project being localized 30+ languages.
the project split pll, bll & dal.
we have on hundred .resx files located in various different folders in base language (english).
we use separate system localization spits out language files in correct format/directory automatically.
once finished there thousands of files import visual studio project!
this become nightmare manage :(
is there way compile localized files separately satellite assemblies , copy them project later?
i want work english files in main vs project , not see localized files.
you can create project houses localized resource files - build these satellite assemblies , copy them main project.
for example:
create new project in existing solution eg: myapp.localized
then change assembly name match name of main application (myapp) , change default namespace (c#) or root namespace (visual basic) match default or root namespace of main application (myapp).
now when build myapp.localized project create satellite assemblies each language-culture in bin folder.
a satellite assembly each language located in subfolder within bin.
copy each language folder main application bin when ready deploy project. (the assemblies must reside inside named language folders)
repeat above each project (dal, bll, pll)
this allows work neutral language in main project , keep other languages in separate project. reducing complexity, build time , clutter in project!
you can find more information at:
http://visualstudiomagazine.com/articles/2005/01/01/make-the-best-of-net-resource-files.aspx
Comments
Post a Comment