The image data processor is configured in the <appsettings> section of the configuration file.

Explanations of the entries added by the designer to your web.config:

• igComponent - Names the plug-in component dll which will be used at run time. The path portion is typically relative to the ASP.NET solution thus the notation "~/bin/" which specifies that the ImageGear component wrapper dll, ImageGear24.Web.ImageDataProcessor.dll, is located in the bin directory below the application aspx pages.
• maxThreadsPerControl - The ImageGear ASP.NET server is capable of running concurrent ImageGear components in different threads. The value of this attribute indicates the maximum number of threads that can be launched housing the component. It is recommended that this value should be set to no greater than twice the number of processors available on the ASP.NET host server machine.
  The following lines need to be edited appropriately, especially when deploying the ASP.NET solution with the appropriate ImageGear License Information. Be sure to remove the comment elements "<!--" and "-->".
  

  C#	Copy Code
  <appSettings> <!--<add key="igSolutionName" value="My ASP.NET Deployment" />--> <!--<add key="igSolutionKey" value="12345, -12345, 12345, -12345" />--> <!--<add key="igLicenseKey" value="1.0qwertyui..." />-->

• igSolutionName - This attribute value should be set with the solution name parameter if one has been obtained for the ImageGear product from Accusoft Corporation. It will depend on the type of license obtained.
• igSolutionKey - The attribute value of this entry should be set with the solution key license if one has been obtained for the ImageGear product. It will depend on the type of license obtained. 
  
  The igSolutionKey may be entered as decimal or hexadecimal values.
• igLicenseKey - The attribute value of this entry should be set with the OEM license key if one has been obtained for the ImageGear product. It will depend on the type of license obtained.
  
  The following lines are required if for some reason you have not installed ImageGear on the target system. The information for these is normally extracted from registry. If for some reason, this information is not available in the registry these attributes must be added in the web.config to reflect the path on the machine hosting the ASP.NET binary folders. If the OS host machine is 64 bit and the ImageGear kit is 32 bit, then the paths are most likely incorrect, as the toolkit is typically installed in the (x86) folder of Program Files. 
  

  C#

  Copy Code

  <add key="igOfficeCoreDir" value="C:\Users\Public\Documents\AccuSoft\ImageGear.NET v24\Bin\OfficeCore" /> <add key="igPdfResources" value="C:\Users\Public\Documents\AccuSoft\ImageGear.NET v24\Bin" /> <add key="igBinaries" value="C:\Users\Public\Documents\AccuSoft\ImageGear.NET v24\Bin" /> <!--add key="igDisableFormats" value="dicom, jpeg2k, office, ps, pdfps, dcraw, dcrawHeaderless" /> --> </appSettings>

• igOfficeCoreDir - For Office formats, the ASP.NET control requires the location of OfficeCore files. The OfficeCore files can be found by either setting this attribute value to the OfficeCore directory or setting the registry key "SOFTWARE/Accusoft/ImageGear/dotNet24" in HKEY_LOCAL_MACHINE with the following value.
  • "OfficeCoreDir" set to the path containing the OfficeCore files and directories, such as libreoffice, lim, node.       
• igPdfResources - For decoding PDF file formats correctly, the ASP.NET control needs the location of where the PDF resource files are stored. The PDF resources can be found by either setting this attribute value to the PDF resource directory or setting the registry key "SOFTWARE/Accusoft/ImageGear/dotNet24" in HKEY_LOCAL_MACHINE with the following value.
  • "PDFResourceDirRoot" set to the path containing the "Resource" directory where the PDF resources are stored.
• igBinaries - Several formats such as PDF have other dynamic libraries pieces which must be located at run time. This attribute value contains the binary folders path to the installed ImageGear toolkit dynamic libraries if not set in the registry. Otherwise, the registry key "SOFTWARE/Accusoft/ImageGear/dotNet24" (or SOFTWARE/Wow6432Node/Accusoft/ImageGear/dotNet24) in HKEY_LOCAL_MACHINE can contain the following value as well.
  • "RootDir" set to the path containing the "Bin" directory where the dynamic dlls are located.
• igDisableFormats – Having the product detecting formats that are not going to be used affects performance and those formats should be disabled (particularly the more complicated format structures). This key will disable the more exotic, complex formats as noted below. Combining comma separated strings disables the formats specified:
  • Dicom - disables the medical Dicom format.
  • Jpeg2k – disables Jpeg 2000 format.
  • Office – disables word, powerpoint and excel formats.
  • Ps – disables the post script pdf format.
  • Pdfps – disables all of pdf including post script pdf.
  • Dcraw – disables Camera raw except for headerless camera raw formats.
  • DcrawHeaderless – disables the headerless camera raw formats. 
• igVerifyDocuments - This setting corresponds to the "Document Verification" checkbox from the Service Settings UI. When enabled, this setting forces ImageGear .NET to validate the format of a document uploaded by the ImageGear.Web.Isis namespace API and reject that document if its format cannot be detected by ImageGear.

• useSvgGzipCompression - When SVG data is used for vector or Office format document transmission, GZIP compression can be used. To enable this functionality, the following line should be added to the appSettings section of the Web configuration file:

  C#	Copy Code
  <add key="useSvgGzipCompression" value="true" />

  In this case, for Web browsers supporting GZIP content compression SVG data will be compressed with GZIP compression. This option allows you to keep the network traffic.