ImageGear .NET, up to version 16.x, used a single assembly for all its features. Starting with version 17, all ImageGear .NET functionality is split into smaller assemblies. The application can use a subset of assemblies, according to its needs.
Perform the following steps to port an application from a single-assembly to a multi-assembly version of ImageGear:
If the application uses file formats metadata API, DICOM Display Settings, or annotations, add casting to classes that expose actual functionality. See Resolving Assembly Cross-Dependencies for details.
A number of methods that belonged to ImGearRasterProcessing Class have been moved to the new ImGearEffects Class. Corresponding methods from ImGearRasterProcessingVerifier Class have been moved to the new ImGearEffectsVerifier Class. See the new ImGearEffects Class for the methods that have been moved to this class.
The following table lists the mapping between ImageGear v16 and current 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 .NET Assemblies provides assembly dependency information. Assembly Dependencies provides assembly dependency information.
| ImageGear v16 Assemblies | ImageGear Current Assemblies |
| ImageGearV16n.dll | ImageGear.Art.dll ImageGear.Core.dll ImageGear.Formats.Advanced.dll ImageGear.Formats.CameraRaw.dll ImageGear.Formats.Common.dll ImageGear.Formats.Dicom.dll ImageGear.Formats.Jpeg2k.dll ImageGear.Formats.Pdf.dll ImageGear.Formats.SimplifiedMetadata.dll ImageGear.Formats.Vector.dll ImageGear.Presentation.dll (FW 3.0) ImageGear.Processing.Advanced.dll ImageGear.Twain.dll |
| IGWinFormsV16n.dll | ImageGear.Art.Forms.dll ImageGear.Windows.Forms.dll |
| IGWpfV16n.dll | ImageGear.Wpf.dll |
| IGWebFormsV16n.dll | ImageGear.Web.dll |