The first step in deploying your application is to package the required ImageGear Runtime components.

ImageGear provides three different options to package the required files:

• (Recommended) The Deployment Packaging Wizard (DPW)
  • Identifies and generates the ImageGear Runtime components required by your application
    It will package all binaries required for individual components. It does not resolve dependencies between components. Refer to Assembly Dependencies for a comprehensive listing of component dependencies.
  • Packages the required components
  • Stores the required files in a specified output folder, creating sub-folders for the Runtime and licensing components
• ImageGear NuGet Packages
• Manual Packaging

Office

If your application requires Office, you will also need to package the OfficeCore dependencies. You should include all Office components and the LibreOffice instance manager needed to use Office features using DPW utility.

In order to use ImageGear.Formats.Office namespace, two conditions must be met:

1. OfficeCore dependencies need to be present on the target machine.
2. ImageGear needs to know the location of OfficeCore.

There are several possibilities to set up the OfficeCore resources correctly:

• use the OfficeCore initialization API by setting the directory with OfficeCore dependencies in the ImGearOffice.Initialize(String) function.
• move the OfficeCore dependencies into the same directory as the ImageGear24.Formats.Office.dll (Bin folder by default).
• set the registry HKEY_LOCAL_MACHINE\SOFTWARE\Accusoft\ImageGear\dotNet24\OfficeCoreDir string value to point to the OfficeCore dependencies directory.

The OfficeCore dependencies directory should contain following components:

• OfficeCore\
  • libreoffice\
  • lim\
  • node\

It is required that every component should have the same bitness as ImageGear24.Formats.Office.dll (i.e., use 32-bit component executables for the x86 .NET target and 64-bit for the x64 .NET target).