What are the best practices for setting localization in an ASP.NET Web Application project in Visual Studio 2008

I feel like I don't have anything at all because I can't find examples that describe what I want to do.

I have a fairly simple ASP.NET web application project for jane that I want to localize. I would like the satellite DLLs to be output, so that later when I want to add a language, I can just add a new DLL.

I created resx files in App_GlobalResources for default culture and Spanish. When I compile tho I don't get a subdirectory under my bin for ES.

If I want to add German or French in the future without recompiling my web application, how do I do it?

Lots of things point to AL.exe, but I haven't seen anyone using it in an ASP.NET application. I can't find any articles pointing out how to set up a localized project / solution in Visual Studio.

+1


source to share


2 answers


I understood what was going on. After I used visual studio to add a new resource file, it added it with a content build action. If it is changed to an embedded resource, the x.resources.dll file will be created in the correct culture directory. You must also set the Access Modifier publicly (I'm sure this is necessary or your main dll won't be able to connect to the culture resource). This will change the Custom Tool property to PublicResXFileCodeGenerator.



0


source


Try this article:

http://www.codeproject.com/KB/aspnet/aspnet-using-localization.aspx



NTN

Colby Africa

+3


source







All Articles