Nuance OmniPage Capture SDK 19.20 Release Notes

Jun 2015

Installation Information

Download and unzip either the 32-bit or 64-bit installation package, browse to the file Setup.exe and run it. You can find the General_ Information.chm file in the Documents folder of your install location; this document serves as a starting point for using the toolkit.

System Requirements

System requirements for a computer used to develop a Capture SDK-enabled application under Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP1 32/64, Windows Server 2008/R2, Windows 7 x86/x64, and Windows Server 2012/R2, Windows 8 x86/x64 (Windows RT not supported in this release):

Pentium 1.6 GHz or higher processor (Pentium 4 is recommended)
512 MB minimum RAM (2 GB recommended, more for working with grayscale or color images)
2 GB free disk space

System requirements for a computer used to run a Capture SDK-enabled application under Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP1 32/64, Windows Server 2008/R2, Windows 7 x86/x64, and Windows Server 2012/R2, Windows 8 x86/x64 (Windows RT not supported in this release)::

Pentium 1.6 GHz or higher processor (Pentium 4 is recommended)
256 MB minimum RAM (1 GB recommended, more for working with grayscale or color images)
300 MB free hard disk space (less if not all recognition modules are distributed)

Getting Started

Read the General Information help: [CSDK19]\Documentation\General_Information.chm.

Help documentation is provided in the form of five HTML files (*.chm). General platform-independent information appears in the General Information Help.

The following help files are provided:

General Information: System requirements, Licensing, Testing and Distributing Applications, etc.
RecAPI: Full reference of all functions, enums and parameters for C++ implementation; it also contains the full RecPDF API reference. This system contains most of the overview and reference topics not repeated for IPRO or Visuals.
IPRO: Full reference of the object model, events, methods and properties.
Visuals: Full description of all visual components. It contains MediumWeight Visuals Namespace and VisualsLib Namespace along with MediumWeight Visuals Controls and Visuals Controls.

Up-to-date version of the documentation files are located in the Documentation folder of the installation media.

User Development tools

The following development tools are considered as "fully supported" by the Capture SDK.

Microsoft Visual Studio 2008-SP1
Microsoft Visual Studio 2010-SP1 (used to produce the Capture SDK)
Microsoft Visual Studio 2012
Microsoft Visual Studio 2013

Other (not tested) development environments with COM and / or .NET Client support should also work with Capture SDK.

Known Issues

Updated documentation files are located in the CD content CSDK\Documentation folder
Beta testers have to delete this file: AllUserAppData\Nuance\License Manager\Info.dat (before installing the RTM version)

Version 19.20

Changes

Service Release
Contains all the fixes applied in v19.11
New API for .NET Applications
It is the replacement of the old P/Invoke interface of the RecAPI. This new API works objects, like other .NET style APIs or .NET Framework itself.
In addition the RecAPI P/Invoke has been reorganized to support this new feature. The new P/Invoke is implemented in two new assembly Nuance.OmniPage.CSDK.CAPI.dll and Nuance.OmniPage.CSDK.ArgTypes.dll. In a new P/Invoke style project use these two assemblies, but we encurage you to use the new .NET API instead.
Old P/Invoke (CAPI_PInvoke.dll) is supported but it might be removed from the next major CSDK Release.
If you use RecPDF P/Invoke and PDF.RecAPIError exception you will have to use this pattern:
try
{
    operation.MergeText(destinationDocument, pageIndex, hpage);
    operation.Execute();
}
catch (PDF.RecAPIError e)
{
    RECERR a = (Nuance.OmniPage.CSDK.RECERR)e.ErrorCode;
}
catch (Exception e)
{
}
New Arabian Language Support
New tag in LANGUAGE enum: LANG_ARA.
New Asian Recognition Engine with trade-off setting
Trade-off setting works with the Asian engine.
Unified Compression Settings
See in KernelAPI.h. They are not available on IProPlus in this release. They have effect on DTXT and Imf outputs. Sample68
RECERR RECAPIKRN kRecSetCompressionLevel(int sid, int CompressionLevel);
RECERR RECAPIKRN kRecGetCompressionLevel(int sid, int *pCompressionlevel);
typedef enum
{
COMPRESSION_FAST,
COMPRESSION_ADVANCED
} COMPRESSION_TRADEOFF;
RECERR RECAPIKRN kRecSetCompressionTradeoff(int sid, COMPRESSION_TRADEOFF CompressionTradeoff);
RECERR RECAPIKRN kRecGetCompressionTradeoff(int sid, COMPRESSION_TRADEOFF* pCompressionTradeoff);
New API for loading image file page without decompressing the image inside
See in KernelAPI.h. It is not available on IProPlus in this release. Sample67
RECERR RECAPIKRN kRecLoadImgDataStream(int sid, HIMGFILE hIFile, HPAGE *phPage, int iPage);
RECERR RECAPIKRN kRecLoadImgDataStreamF(int sid, LPCTSTR pFilename, HPAGE *phPage, int nPage);
RECERR RECAPIKRN kRecDecompressImgDataStream(int sid, HPAGE hPage);
RECERR RECAPIKRN kRecFreeImgDataStream(int sid, HPAGE hPage);
RECERR RECAPIKRN kRecLoadImgDataStreamMC(int sid, BYTE *lpBuf, size_t bufLen, LPCOMPRESSED_IMG_INFO lpCImg, HPAGE *phPage);
RECERR RECAPIKRN kRecLoadImgMC(int sid, BYTE *lpBuf, size_t bufLen, LPCOMPRESSED_IMG_INFO lpCImg, HPAGE *phPage);
Supported compression: IMG_COMPRESSION enum. More content goes here
New API for creating PDF searchable output
See in KernelAPI.h. It is not available on IProPlus in this release. Sample66
RECERR RECAPIKRN kRecMakePagesSearchable(int sid, LPCSTR pFilename, int fromPage, const HPAGE* ahPage, int nPage, IMAGEINDEX iiImg);
RECERR RECAPIKRN kRecConvert2DTXTEx(int sid, const HPAGE *ahPage, int nPage, IMAGEINDEX iiImg, LPCTSTR pFilename);
New See in KernelAPI.h. It is not available on IProPlus in this release.
#define IMF_PDF_AS_IMAGE 1
#define IMF_PDF_NO_TAGS 2

#define IMF_PDF_ANN_NOTE (4 << 0)
#define IMF_PDF_ANN_LINK (4 << 1)
#define IMF_PDF_ANN_TEXT (4 << 2)
#define IMF_PDF_ANN_LINE (4 << 3)
#define IMF_PDF_ANN_SQUARE (4 << 4)
#define IMF_PDF_ANN_CIRCLE (4 << 5)
#define IMF_PDF_ANN_POLYGON (4 << 6)
#define IMF_PDF_ANN_POLYLINE (4 << 7)
#define IMF_PDF_ANN_HIGHLIGHT (4 << 8)
#define IMF_PDF_ANN_UNDERLINE (4 << 9)
#define IMF_PDF_ANN_SQUIGGLY (4 << 10)
#define IMF_PDF_ANN_CROSSOUT (4 << 11)
#define IMF_PDF_ANN_STAMP (4 << 12)
#define IMF_PDF_ANN_CARET (4 << 13)
#define IMF_PDF_ANN_PENCIL (4 << 14)
#define IMF_PDF_ANN_POPUP (4 << 15)
#define IMF_PDF_ANN_FILEATTACHMENT (4 << 16)
#define IMF_PDF_ANN_SOUND (4 << 17)
#define IMF_PDF_ANN_MOVIE (4 << 18)
#define IMF_PDF_ANN_FORM (4 << 19)
#define IMF_PDF_ANN_SCREEN (4 << 20)
#define IMF_PDF_ANN_PRINTERMARK (4 << 21)
#define IMF_PDF_ANN_TRAPNET (4 << 22)
#define IMF_PDF_ANN_WATERMARK (4 << 23)
#define IMF_PDF_ANN_3D (4 << 24)
//! Setting & getting load flags for pdf file loading
/*! The kRecSetImfLoadFlags function set an IMF Load Flags combination
    \param[in] sid
    Settings Collection ID.
    \param[in] fFlag
    The IMF Load Flag combination
    \retval RECERR
*/
RECERR RECAPIKRN kRecSetImfLoadFlags(int sid, DWORD fFlag);
RECERR RECAPIKRN kRecGetImfLoadFlags(int sid, DWORD *pfFlag);
ITest is able to run with any CSDK Kit
New OEM licensing mode – “Internal mode”
- Does not require .NET
- Does not require the NuanceLS.exe running in any way (in service or in side-by-side process)
- Does not use TCP/IP
- Does not require Internet connection in runtime/deployment at all
- Standard OEM license keys issued by Manufacturing from the beginning of 2014 can be used
- Does not require new API – just slight modification in application source code
General Improvements in PDF MRC Output
.

Technical Notes

The following issues are added to the documentation.

Changes in P/Invoke style newly developed applications
Enums and Structures moved to a separate assembly Nuance.OmniPage.CSDK.ArgTypes.dll and P/Invoke itself lives int Nuance.OmniPage.CSDK.CAPI.dll. Newly developed P/Invoke applications need to add these assemblies to the References. Old CAPI_PInvoke.dll is deprecated, it won't be supported from the next major CSDK Release.
Please study the new API for .NET Application.

Version 19.11

Changes

Service Release
Contains all the fixes applied in v19.00
Uninstall v19.00 (32-bit and 64-bit) before installing v19.11
Form Template Editor v1.10 requires CSDK v19.11. CSDK 19.00 and 19.11 side by side installation is not supported in this release. In redistribution, any CSDK versions can coexist on same computer (in different installation folders).
Finetuned Form Template Editor and Form Template Processing
- No error returned if the template contains reference anchors but does not contain positional anchors (bugfix).
- More accurate determination of zone positions when the template contains only two positional anchors.
- Processing camera images: more accurate determination of zone positions when the template does not contain positional anchors (only reference anchors).
- Better handling of ambiguous reference anchors (select the best one when there are more anchor candidates).
- Better calculation of confidence when the template contains only two positional anchors.
- Better calculation of confidence when the template contains reference anchors but does not contain positional anchors.
PDF MRC output improvements
Better layout separation for smaller MRC PDF size. Even the output PDF files are significant smaller, the new algorithm is little bit slower. The application can switch back to previous MRC mode using "KERNEL.IMF.PDF.MRC.TradeOff" = MRC_FAST(0)
PDFA/1a /2a improvements
Contains all the fixes applied in v19.00
Formatted Layout Header/Footer detection improvement
Better header / footer detection
BAR engine development
New setting kernel.OcrMgr.BarCheckBarTypes.Enable.C39_C39EXT is introduced for automatic barcode recognition in case of BAR_C39 and BAR_C39_EXT barcode type. If this setting is true and BAR_C39 and BAR_C39_EXT barcode types are enabled at the same time, the recognition engine automatically decides which barcode type is more likely to be encoded in the barcode.
RecIproPlus VS2005 support binaries removed
VS2005 ISApp and VSApp samples also removed
Manual Activation
Web Page: http://activation.scansoft.com/csdkactivation
New command line switch to get the hardware finger print used by Nuance Licensing:
nuancelt.exe hwfp -> creates a csdk_hwfp.txt file under the user's my documents folder.
New CSharp Sample Application for IProPlus/Nuance.OmniPageSDK.IproPlus and some Visuals/Nuance.OmniPageSDK.ToolBoxes Assemblies
[CSDKInstallPath]\Samples\HowCouldWeUseIt is a demo application for the usage of IProPlus and some parts of the Visuals. Load build and run the sample see the sources.
Ignore the source control warning dialog when opening HowCouldWeUseIt.sln for the first time
FM_ASIAN filling method
The use of this filling method is not necessary. In most cases there is no need to manually specify zone parameters. In the few remaining cases you may use FM_OMNIFONT even for Asian.

Version 19.00

New features

New RecAPI functions and Form Template Editor for Form Processing)
Template definition step:
Scanned empty or filled form images can be used for template creation using the new Form Template Editor standalone desktop application. (CDContent\FormTemplateEditor\setup.exe) The Logical Form Recognition (LFR) module helps the creation phase by automatically detecting form fields. The created form templates can be tested within the Form Template Editor.

Processing step:
During form processing, OPSDK automatically selects the appropriate template for each scanned image. It matches the selected template to the actual image (form registration), recognizes the form fields, and converts the captured data to the selected output formats.

Batch Separation:
Form templates and form template libraries can be used for automatic Job Separation as well. In this case form templates should contain one or more Selection Anchors only.

Sample #64 demonstrates a basic form matching and processing workflow in SamplesC.exe

The new set of Form Processing functions are available on RecAPI and RecAPI-P/Invoke only. IproPlus does not support this new feature in this release.
ePub Output Converter Introduced
New output formats introduced for supporting Electronic Publications.
Converters.Text.ePub
Converters.Text.ePubSimple
Converters.Text.ePubPoem
Book Mode
This output format retention mode is used for multipage book-like inputs.
Processing.Mode = PROCESSING_BOOK
Deprecated Output Converters Revoked
Converters.Text.Excel97
Converters.Text.Word97
Converters.Text.RTF97
Converters.Text.RTF6
Converters.Text.eBook
Converters.Text.MicrosoftReader
Converters.Text.RTF2000SWord
Converters.Text.WORD2000

New Barcode Types introduced in the BAR engine
Existing types newly supported by BAR:
BAR_2of5
BAR_C93
BAR_C39_NSS
BAR_MAT25
BAR_QR
BAR_DMATRIX
BAR_PLANET
BAR_PATCH

New barcode types supported by BAR only:
BAR_CODE11
BAR_ItalianPost25
BAR_MSI
BAR_BOOKLAND
BAR_ITF14
BAR_EAN14
BAR_SSCC18
BAR_DATABAR_LIMITED
BAR_DATABAR_EXPANDED
BAR_4STATE_USPS
BAR_4STATE_AUSPOST
Kadmos Handwritten Engine 5.0g
ICR2 Kadmos engine updated to 5.0g
AmpLib Barcode Engine 6.2.8.6
Barcode AmpLib engine updated to 6.2.8.6
Output File Splitter
CSDK text output can be split into multiple output files, with this controlling file size and/or page number. Two new settings are implemented. They control the output splitter. One of them specifies the maximum number of pages in each output. The other one specifies the maximum size (in bytes) of each output. If both are given, the splitter splits the one that comes first.

for PDF Image output:
Kernel.IMF.PDF.SplitMaxSize
Kernel.IMF.PDF.SplitMaxPages

for DTXT/PDF output:
Kernel.DTXT.PDF.SplitMaxSize
Kernel.DTXT.PDF.SplitMaxPages

for all Formatted outputs:
Converters.Text.ConverterName.SplitMaxSize
Converters.Text.ConverterName.SplitMaxPages

Camera Image handling improvements
Obtaining camera flag from EXIF info (to determine whether an image came from a digital camera)
Auto-deskew option can be turned on or off (if on, the program determines whether to apply 2D or 3D deskewing: for normal or camera images) Automatic resolution (DPI) estimation
½ resolution enhancement (automatic preprocess step: if camera image contains very high resolution characters - over 300 DPI- image resolution is decreased to 300 DPI optimal for OCR engine)
Shading correction
New binarization method
Modified workflow for camera images for better OCR results (resolution enhancement and text line straightening are applied to images coming from a digital camera)
MP3 Audio output support
New output converter Converters.Text.Audiomp3
for Premium quality Audio Output
Support for Nuance Vocalizer for better audio quality
See details in Technical Notes section

New Assembly for 1st Class .NET support to IproPlus
Add Reference to Nuance.OmniPageSDK.IproPlus.dll assembly to access IproPlus in your .NET Form application. See the NewISAppCSharp100 sample application.

New Assembly for 1st Class .NET support to Visuals
Add reference to Nuance.OmniPageSDK.ToolBoxes.dll assembly to access Visuals in your .NET Form application. See the NewVSAppCSharp100 sample application.

Thai engine integration
Thai language setting is enabled in V19. DTXT Text, DTXT XML and DTXT searchable PDF outputs are supported in this release.
Image processing integration: despeckling, auto orientation, deskew and auto zoning. Auto orientation, deskew and zoning modules are not designed for Thai and there are no plans to adjust them to Thai. Only normal orientation without skew will be handled. Zoning is done by Nuance's Legacy algorithm which has a limited support for magazines.
Additional Language support file is ttfth.rec

Technical Notes

The following issues are added to the documentation.

Changes in error handling of kRecProcessPagesEx(), RecProcessPagesEx() and RecProcessPages() functions
When low level error or warning conditions occur, functions return with API_ERRORS_HAPPENED_WARN or API_WARNINGS_HAPPENED_WARN. If the application requires a return value, it can use (k)RecGetRPPErrorList() to get the error or warning details.
For instance, to get first error:
rc = RecAPIPlus.RecProcessPagesEx(0, outputFile, iFiles, null);
if (rc == RECERR.API_ERRORS_HAPPENED_WARN)
{
    RPPERROR[] rppErrs;
    RecAPIPlus.RecGetRPPErrorList(out rppErrs);
    for (int i = 0; i < rppErrs.Length; i++)
    {
        if (rppErrs[i].rc > 0)
        {
            rc = (int)rppErrs[i].rc;
            break;
        }
    }
}
For fully functioning CSDK, .NET Framework role should be turned on on Windows Servers
JBIG2
Default compression is set to lossless (if needed, user can set it back to lossy, using appropriate settings). See the documentation.
Nuance Vocalizer support for premium quality audio
CSDK 32-bit version supports the use of Vocalizer engine for better audio quality. Vocalizer engine has be installed.
The user's installer program has to create these registry items (also on developer PC):

On x86 OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\Nuance\Vocalizer Expressive]
"InstallPath"="... location of the Vocalizer engine (ve.dll)"

[HKEY_LOCAL_MACHINE\SOFTWARE\Nuance\Vocalizer Expressive\SAPI5]
"Vocalizer Expressive"="... location of the Vocalizer engine (ve.dll)"

On x64 OS:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Nuance\Vocalizer Expressive]
"InstallPath"="... location of the Vocalizer engine (ve.dll)"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Nuance\Vocalizer Expressive\SAPI5]
"Vocalizer Expressive"="... location of the Vocalizer engine (ve.dll)"

(On x64 OS some more registry changes may be needed:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32
“msacm.l3acmp”=”C:\Windows\SysWOW64\l3codecp.acm”
)
Value of the UNICODE_MISSING define changed
The new value is 0xFFFC.
VS2005 Sample Application removed from V19
V19 further supports building applications with VS2005.
64-bit Visual Controls are not supported by Visual Studio
You cannot use the Visual Studio resource editor for editing dialogs that contain CSDK Visuals when the Solution Platform is x64. A 32-bit program, like Visual Studio, does not support 64-bit ActiveX hosting and displaying. If you develop a 64-bit application, you have to edit the resource dialogs with active Win32 Solution Platform.
Activation and Callhome part of the Nuance License Service require IPv4 protocol to be installed.
OEM type runtime licensing (pre-activated, validation disabled) supports both IPv4 and IPv6 protocols on local networks.
Selected Output formats .NET 4 Framework installed
DOCX, PPTX, XLSX and XPS outputs use the .NET 4 Framework. If your application produces these outputs, your installer must install .NET 4 on destination computers unless it is already present.
CSDK19 with OEM type runtime licenses (pre-activated, no callhome) uses .NET4 Client profile version. License Activation and callhome require .NET4 Extended version.
Error message may appear during .NET Framework 4 Setup.
In this case you must install the Windows Imaging Component before CSDK19 setup. See: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=32
C++ Exceptions may occur under Debugger
Add a new C++ Exception to the Debugger exception handling to avoid unwanted debugger breaks:
- Click Exceptions... menu under the Debug tab to bring about the Exceptions dialog box.
- Click the Add... button.
- Select the C++ Exceptions from the drop-down list.
- Enter the name PDF_PROGRESS.
- Click OK.
- Leave the Thrown checkbox unchecked under C++ Exceptions - PDF_PROGRESS
RecProcessPagesEx working from scanner requires an existing HWND
// C/C++ Application Mainframe Window or GetDesktopWindow() for console programs
HWND hwnd = GetDesktopWindow();
HSETTING hSts;
kRecSettingGetHandle(NULL, "APIPlus.HWND", &hSts, NULL);
kRecSettingSetInt(0, hSts, (int)hwnd);
// PInvoke
int hwnd = (int)form.Handle;
int hSett;
rc = RecAPI.kRecSettingGetHandle("APIPlus.HWND", out hSett);
RecAPI.kRecSettingSetInt(0, hSett, hwnd);
// IproPlus.NET
Console.m_oEngine.WindowHandle = (int)GetHWND();
// RecIproPlus
Engine->SetWindowHandle(GetAppMainWnd());
RecIproPlus interface is deprecated
This may be removed from future releases.
In IproPlus C++ applications IUnknown based source interfaces must be marshaled from V19
RealSpeak Solo Merge Modules moved to C:\Program Files\Common Files\Merge Modules folder
Your installer must pick these files from here. The CSDK Distribution Wizard no longer copies them.
CSDK16 Workflow files are not compatible with CSDK19
Installation on Windows Server 2008 R2
Run AutoRun.exe or Setup.exe as Administrator.
VS2010-VS2012 converted MyCApp90.sln
If you rebuild MyCApp90.sln using VS2010, you need take some extra steps. Change the following properties of MyDtksam90 project in VS2010-VS2012 after the conversion:
General->Output Directory = ..\..\Bin
General->Target Name = MySampleC
Linker->General->Output = "Inherit from parent or project default"
Saving XPS image only output
The application must call CoInitialize(NULL) when it wants to save XPS image files using kRecSaveImg()to set the required STA mode. For more information, see (http://msdn.microsoft.com/en-us/library/windows/desktop/ms678543(v=vs.85).aspx)
Application using kRecInitS and RecInitPlusS at the same time
The application must include the following header files, respectively:
#include "...\include\KernelAPIS.h"
#include "...\include\RecApiplusS.h"

In addition, the function kRecInitS must be called before RecInitPlusS. This usage is different from the kRecInit/RecInitPlus pair

//If the program uses OEM licensing
rc = kRecSetLicenseS(OEMLicenseFile, "Your public key");

rc = kRecInitS("C:\\Program Files\\Nuance\\OPCaptureSDK18\\Bin\\", NULL, NULL);
rc = RecInitPlusS("C:\\Program Files\\Nuance\\OPCaptureSDK18\\Bin\\", NULL, NULL);

// Your code comes here

RecQuitPlusS();
kRecQuitS();

Amplib license file
By default the DevKit searches AMPLib OEM license files on their installation path beside KernelAPI.dll. If the application calls the RecAPI function kRecSetLicense and defines a path, the DevKit will search AMPLib license files on this path.
Multiple scanner support in CSDK
Using the Scanner Wizard, you can setup multiple scanners to be used in your integrating application. Due to some unresolved scanner-specific issues, the installed scanner settings might conflict. Therefore it is highly recommend not to set up more than one scanner at a time for a single application.
Font cache file
When CSDK starts for the first time, a font cache file fontlist6.opf is created in the %ALLUSERSPROFILE%\Application Data\Nuance\OmniPageCSDK19 folder. If you install any new fonts on the system, you have to delete this file. It will be recreated with an updated font listing when the kit starts again.
On Vista 64bit OS, VSAppCSharp80.exe, VSAppCSharp90.exe, VSAppVBNET80.exe, VSAppVBNET90.exe applications do not run.
Rebuild them with the x86 CPU setting.
.NET 1.1 Framework is not supported by RecAPI P/Invoke and IproPlus.NET
Only .NET 2.0 Framework compatible applications can use these interfaces.
OEM runtime licenses should not be used on a computer with the Capture SDK development environment installed.

Reason: As it is a runtime license, it is intended to be used and tested in a runtime environment.
Resolution: Test your OEM licensed application on a clean test computer with no CSDK installed.

Two reasons exist against testing your distribution and runtime license together on a test computer with no CSDK and other development environments installed:

1.       Your clients’ computers should not contain any development environment that includes common binaries and registry settings. Distribution testing on a development computer can therefore be misleading, as the developer machine contains all those binaries and registry settings, and will not pinpoint any installation problems.

2.       As a Fixed Volume License (FVL) and an OEM license are merged in memory during runtime, the OEM license test on a developer computer will fail, because the developer license is merged. Your developer license, being an FVL, can contain more enabled features than you need in a particular application. Therefore, for example, if you forgot to ask for an Asian bit in the OEM file but you have it in the developer license, your program will run Chinese recognition without problems on the developer machine but not on the client machine.

There are two simple solutions to run and debug your application with the CSDK distribution file set but still in a development environment (you can use either of them):

1.       Use simple logic in your code: when the OEM file is not present, the function kRecSetLicense should not be called. If it is run on the developer machine where the OEM license file is not present, the application will use the developer license.

2.       Use conditional compilation to exclude the code line containing the function kRecSetLicense when making a Debug build. You can debug your application with the CSDK distribution file set using the developer license available on the developer machine.
Redistributable Microsoft file sets for deployments
In each case the deployment for your own Capture SDK-enabled application requires you to include one of the redistributable file sets from Microsoft. The Distribution Wizard in the Capture SDK provides you with hints on which merge modules contain the redistributable file set necessary for your particular deployment. This section tries to simplify your options:
- As the Capture SDK was built with Microsoft VS 2010, the Distribution Wizard will advise several merge modules of VS 2010. Microsoft Visual C++ 2010 Redistributable Package (x86) – VCRedist_x86.exe 10.0.30319.1, covers all the necessary Microsoft binaries from those merge modules. It can be downloaded from:
  http://www.microsoft.com/downloads/en/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84
  VS2010-SP1 redist (en_visual_c++_2010_sp1_redistributable_package_x86_651767.exe) is also appropriate for CSDK19 using version 10.0.40219.1 or higher.

An up-to-date version of this file is located in the root folder of the installation media.