Distributing an ImageGear Application

We do not recommend that you compile using AnyCPU, as some resources are platform-specific.
A managed code application using the 32-bit version of ImageGear .NET must target the x86 platform. The toolkit will be running as a 32-bit process on a 32-bit machine or as a 32-bit process on a 64-bit machine.
A managed code application using the 64-bit version of ImageGear .NET must target the x64 platform. The toolkit will be running as a 64-bit process on a 64-bit machine.

Starting with v22, ImageGear .NET provides NuGet Packages to simplify the packaging process. NuGet packages make it easy to add, remove, and update libraries and tools in Visual Studio projects that use the .NET Framework.

If, however, you prefer to handle this manually, this topic provides information about the assemblies and their dependencies.

You must always distribute your application along with the assemblies that enable the capabilities you're using and their dependencies. See Assembly Dependencies.

In addition, you must include the following:

If Your Application Uses...	Include...
ImageGear.Formats.JPEG2K	igjpeg2k22nu.dll
ImageGear.Vector and/or ImageGear.Formats.[CAD/CGM/DGN/DWF/HPGL]	igvect22nu.dll
ImageGear.Formats.CAD	igvect22nu.dll igcad22nu.dll
ImageGear.Formats.DWF	igvect22nu.dll igdwf22nu.dll
ImageGear.Formats.PDF	See Distributing PDF and PS Fonts and Libraries with an Application
ImageGear.Recognition	See Distributing Recognition Engine Files with an Application
ImageGear.Web.DataProviders and/or ImageGear.Web.UI	See Distributing an ImageGear for an ASP.NET Application