How has the use of Resource Files been improved in Visual Studio .NET?
In Visual Basic 6.0, resource files are used to store the language specific data that your application uses. This data can be strings, images, or other types of resources. A VB 6.0 project can only contain a single resource file. One way to add localization features to your application is to place versions of all your data for the different supported languages in a single resource file. Alternatively, you can store each language in different resource files; the resource files are compiled into independent DLLs. At run time, you dynamically load the DLL that contains the localized resources you need. Visual Studio .NET provides a much more integrated level of support for localization. If you set the Localizable property of your form to True, Visual Studio creates a resource file for that form and stores the text strings for different languages in separate resource files that are automatically compiled into satellite DLLs. These DLLs are loaded dynamically and automatically at run time,
Related Questions
- My company followed localization and internationalization best practices during development, should we still do testing before getting our resource files translated?
- How do I instruct DashO™ to include resource files (non-class files) in the destination ?
- How has the use of Resource Files been improved in Visual Studio .NET?
