Configuring .NET Components

Alchemy CATALYST supports all versions of the Microsoft .NET framework. It can create optimised and unoptimised language assemblies, and can be configured to use various framework editions when parsing files and automatically signing language assemblies.

.NET Satellite Assemblies

	Extract only modified resources to satellite assemblies: Select this option to create optimized language assemblies which only contain modified resources. If this option is deselected, Alchemy CATALYST will create verbose or unoptimized language assemblies which will contain all resources from the original language assembly.
	Extract original assembly when extracting satellite assemblies: Select this option to create the base language assembly when generating the variant language assembly.
	Save Assembly linker parameters to text file: Select this option to create a text file containing all of the assembly linker parameters Alchemy CATALYST uses in building language assembly files. This file is stored is the same location as the language assemblies.

Signing Assemblies

	No Signing: Select this option if language assemblies are to be created and not signed.
	Auto detect public keys and delay sign satellites on creation: Select this option if you'd like Alchemy CATALYST to locate the public keys within the original base assembly and use these to sign any satellite assemblies created.
	Use Key file (SNK): Use this option to specify a digital signature key file to be used when building language assembly files. The SNK file will be used by Alchemy CATALYST to delay-sign a language assembly.
	Delay/Fully Sign: Select the type of signing required for a .NET application.

User Messages

	Show all Microsoft .NET/Resx messages: Select this option to show all .NET warning and information messages in the Results Toolbar during file insertion and extraction. This can be helpful when investigating what needs to be translated in a large .NET application.
	Show extended WPF properties by default: Select this option to display all properties of a WPF control in the Translators Toolbar.

Using Language Assemblies

Alchemy CATALYST supports two types of language assemblies. These can be used at any stage throughout the localization of .NET applications and each has certain benefits over the other.

	Optimised assemblies: These are language assemblies containing only modified resources. Since they do not contain an applications complete resource set, optimized assemblies cannot be localized using standard visual tools. As such, optimized assemblies are typically built at the very end of a localization process only.
	Unoptimised assemblies: These are language assemblies that contain an applications complete resource set. As such they can be localized using any of the visual tools that come with Alchemy CATALYST.

Since optimized language assemblies contain only a subset of an applications resources, they tend to be much smaller in size than unoptimized language assemblies. However they can be difficult to manage in a localization project , as not all the resources are present in the file itself.

This is why Alchemy CATALYST provides the ability to create unoptimised assembly files. While these files may be larger in size, they do contain a complete set of application resources and consequently can be localized using visual tools.