.NET Files

.NET Files (.NET Resource Files)

WPF

Supported .NET Resource Files

FILE TYPE	DESCRIPTION	TRANSLATED TARGET FILE TYPE
RESX	.NET Windows form; XML resource file. Contains: – one Windows form – menu (none, one, or more) – toolbar (none, one, or more)	Same as the source (.resx) or the binary .resources file.
RESOURCES	Binary resource file; a compiled .resx (XML) resource file.	Same as the source (.resources) file.
TXT	.NET text file- text only. For each individual item the file contains the ID, the text, and, optionally, a comment.	.NET text file (.txt), XML resource file (.resx), or binary resource file (.resources). Text encoding: ASCII, Unicode or UTF-8.
EXE	Windows Forms Application (Executable)	Satellite DLLs (.dll)- one for each target language. NOTE: A single assembly resource file of an .exe file can be written to an XML resource file (.resx) or to a binary resource file (.resources). This is used by RC-WinTrans to make a single form for editing available with an external resource editor.
DLL	Windows Control Library	Satellite DLLs (.dll)- one for each target language. NOTE: A single assembly resource file of a .DLL file can be written to an XML resource file (.resx) or to a binary resource file (.resources). This is used by RC-WinTrans to make a single form for editing available with its external resource editor.

Strong-Named Assembly Files

The converter for .NET files is designed to handle strong-named assembly files. The strong-named target assemblies are written as "delay signed." It is therefore necessary to "sign" those target assemblies before they can be used. Usually a private key that is not available to RC-WinTrans is used to sign an assembly with a strong name. The converter macro that calls the RESX converter (macros file: "SystemMacros"; module: "ConvRESX") can be customized to also sign a strong-named assembly if the key file is available.

Menu Resource Structure

If available, the converter for .NET files will extract structural information (e.g., the grouping of controls and menu structures) out of the source code file (e.g., C# or VB file). This is contextually important information that the converter also stores in the translation data file. However, due to the technical construction of the file as it was made by Microsoft, some kinds of structural information (e.g., the menu hierarchy) are not included in the resource file- instead they are contained in the source code file. Therefor this information can only be read by the file converter if the source code file is available (placed in the same folder as the corresponding RESX resource file).

NOTE: The structure information of menu resources are not available for assembly files. Consequently it is not possible to generate a context view for menus.

User Controls

All of the data contained in .NET user controls is read by the converter and visible within RC-WinTrans. It is possible to configure the converter to support the conversion from user data types into data types known by RC-WinTrans to be translatable strings.