Support localized messages for .NET client interfaces
- Last Updated: March 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
When ProxyGen builds the .NET proxy, it copies the required .NET runtime assemblies to the proxy generation output directory. For the message assembly, only the resources for the language matching the current local language are copied to the output directory. If you need to support a different language, you must manually copy some additional files to the output directory.
To support an alternative language or more than one language, you must copy the language resources from one of the following locations depending on your generation option:
-
Strong-named and digitally-signed runtime assemblies —
Copy the resource for the languages you want to support from the
following directory:
OpenEdge-install-directory\dotnet\deploy\strongnamed-signed\ -
Digitally-signed only runtime assemblies — Copy the resource
for the languages you want to support from the following directory:
OpenEdge-install-directory\dotnet\deploy\signed\ -
Strong-named only runtime assemblies — Copy the resource
for the languages you want to support from the following directory:
OpenEdge-install-directory\dotnet\deploy\strongnamed
For example, if you want to support a French deployment for a signed-only environment, copy the fr directory from OpenEdge-install-directory\dotnet\deploy\signed\ to your proxy generation output directory.