ImageGear for Silverlight, up to version 16.x, used multiple assemblies for all its features. However, starting with version 17, ImageGear for Silverlight provides a new multiple assemblies breakdown to keep it consistent with the ImageGear for .NET product. The application can use a subset of assemblies, according to its needs.

Perform the following steps to port an application from a previous multi-assembly of ImageGear:

1. Replace the reference to the old ImageGear assembly with references to ImageGear assemblies that the application needs to use.
2. Add initialization for components that require it. See Assembly Initialization for the list of components that require initialization.
3. All methods that belonged to ImGearRasterProcessingAdv class have been moved and combined with ImGearRasterProcessing Class. Corresponding methods from ImGearRasterProcessingAdvVerifier have been moved to ImGearRasterProcessingVerifier Class.
4. Drawing methods that belonged to ImGearPageDisplay Class have been moved to the new ImGearPresentationPageDisplay Class, which is an advanced version of the ImGearPageDisplay Class. ImGearPresentationPageDisplay Class inherits ImGearPageDisplay Class and provides an API for displaying images and annotations. Silverlight applications should use ImGearPresentationPageDisplay Class instead of ImGearPageDisplay Class. Please refer to the ImGearPresentationPageDisplay Class section of Displaying Images for more details.

The following table lists the mapping between ImageGear v16 and v19 assemblies. Note, however, that you do not have to use all of the assemblies. You only need to use assemblies that provide the desired functionality, and the assemblies upon which they depend. ImageGear for .NET Assemblies provides assembly dependency information. ImageGear for Silverlight Assemblies provides assembly dependency information.