Reason

This article explains how to insert .NET binary files into a TTK and explains how to review the results of the insertion.

Example of results in Catalyst on inserting a .NET file

 

Solution

Inserting files in Alchemy Catalyst

In order to insert your .NET application into Alchemy Catalyst for translation, you will need to insert each individual file containing Localisable elements. Furthermore, you will need to have any linked assembly present in the same directory as the file you are inserting. This is so that Alchemy Catalyst can load the necessary resources needed to render the visual views. This means that Alchemy Catalyst loads the linked assemblies in the background in order to allow to run successfully in visual mode. It doesn't mean that the file has been inserted for translation.

If you are inserting a main assembly file, you can have the linked assemblies in locale specific subdirectories referenced within.
For example, SampleApp.exe main assembly has linked assemblies in an en-US sub-directory:

In the development environment the localizable attribute needs to be set to true on Winforms resources. If Catalyst finds a resource that it thinks may contain a Winform with the localizable attribute set to false then it notifies the user.  The localizable attribute only applies to Winforms. Alchemy Catalyst will refer to other resources as localizable or not but it is not referring to the attribute.

 

Sample insertion and explanations

The following is an example of a .NET dll inserted into Alchemy Catalyst with comments on particular entries of interest.

Starting file insertion...

Inserting File C:\dot net\Sample.PIC.Configuration.dll

Sample.PIC.Configuration.dll is a Microsoft .NET 2.0 or later assembly.

Loaded for parsing: Sample.PIC.Configuration.dll using .NET Framework version 2.0

Found 130 sections 119 of which have localizable content.

 

The following are empty resources, should the Localizable property have been set to true ?

Sample.PIC.Configuration.FeatureOptionAssignmentControl.resources

Comment: In the development environment the localizable attribute needs to be set to true on Winforms resources. If Catalyst finds a resource that it thinks may contain a Winform with the localizable attribute set to false then it notifies the user.

No Localizable content: Sample.PIC.Configuration.Properties.Resources.resources

Comment: If the localizable attribute is not mentioned, then it not deemed to be relevant. The resource does not appear to contain a Winform. It does not contain any other type of localizable content either though, like strings, so Alchemy Catalyst reports it.

 

Missing assembly

While inserting .NET files in Alchemy Catalyst, you may get a Missing assembly: assembly_name entry in the results pane.

In this case you need to make a copy of the assembly in the root directory from which you are inserting the .NET file from.

Alchemy Catalyst's WPF solution will report missing satellites if the main assembly references them. It won't for Winforms.

 

Notes

You can't insert .NET binary files properly from the network. This security restriction is coming from the .NET framework and not from Alchemy Catalyst. The Framework will not allow to run code across the network.

However, you can achieve insertion from the network if you use the Security Adjustment Wizard to modify the level of trust granted to assemblies coming from Local Intranet. You need go to Control Panel, Administrative Tools, .NET Framework 2.0 configuration tool, click on Configure code access security Policy and click on 'Adjust zone security'. In there you can increase the level of trust given to the local intranet. This should allow Alchemy Catalyst to load your assemblies from a network location.

 

Related topics

 

Products or Versions Affected

  • Alchemy CATALYST 8.0  and greater