Microsoft .NET Framework Errors

When Inserting file into a Project TTK, Alchemy CATALYST will display useful information in the Results Toolbar. This can help a localization engineer debug .NET applications and .resx files and locate dependant assemblies. The following errors can be generated during file insertion operations.

Unable to resolve type

This situation arises when Alchemy CATALYST cannot determine the base type of a control/ Winform Microsoft name for a .NET Dialog Panel. . To resolve this, you need to place a copy of the assembly containing the control/Winform in the \BINDEPENDs folder, or in the same folder as the .NET application file.

Possible unmapped type property for a form

This situation arises when Alchemy CATALYST cannot uniquely determine if an object is derived from a base Winform object. To resolve this, you need to declare this object as a form in the CONTROLMAPPING.XML file which can be located in your Alchemy CATALYST installation folder.

Unable to complete .NET Framework initialization

This situation arises when Alchemy CATALYST cannot initialise the .NET framework on your PC. Please contact your network administrator to verify that your machine is capable of running the Microsoft .NET Framework 2.x.

Type Not Found

Alchemy CATALYST displays this information if it cannot determine the Type information of a control. In most cases this means that it cannot be found in the .NET application or any other assembly files known to Alchemy CATALYST. You can resolve this by placing a copy of the missing assembly file, containing this control, in the \BINDEPENDS folder. This folder is located in your Alchemy CATALYST installation folder.