SmartZone v7.1 - Updated
Upgrading from SmartZone OCR 5 to SmartZone OCR 7
Getting Started > Upgrading SmartZone OCR > Upgrading from SmartZone OCR 5 to SmartZone OCR 7

This section describes how to upgrade from SmartZone 5 to SmartZone 7. While generally you'll be able to replace SmartZone 5 with SmartZone 7, there are a few important changes you may need to consider.

Assembly Changes

Projects must now target .NET Framework 3.5 or later to build with the SmartZone OCR assembly.

The assembly file name has been renamed from Accusoft.SmartZoneOCR5.Net.dll to Accusoft.SmartZoneOCR.Net.dll. Project references must be updated to use the new assembly.

Some native libraries that were previously integrated in the Accusoft.SmartZoneOCR.Net assembly are now included as separate dlls. These libraries will be extracted to the same directory as the assembly when using the Nuget Package. For Windows the libraries are named Accusoft.SmartZoneOCR.Common.dll and Accusoft.SmartZoneOCR.Common64.dll. For Linux distributions, the name of the file is These need to be included when redistributing any application that uses the SmartZoneOCR SDK.

Licensing Changes

Standard Edition licenses are no longer supported and will not be issued for SmartZone OCR 7.

Runtime Changes

There is now a runtime dependency with Microsoft Visual C++ for VS2015. Although SmartZone OCR 7 includes Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019 and 2022 dependencies for local deployment, it is preferred that Windows host machines install Universal CRT using Microsoft Windows Update.

Performance Changes

SmartZone OCR 7 uses a different OCR recognition engine. Expect some differences in speed and accuracy compared to SmartZone OCR 5.

To retain multi-threaded support, OCR recognition is performed from child processes. Each child process will require between 100 and 350 MB of RAM to operate depending on the operating system, recognition language chosen, input image size, and input image content.

API Changes

The class Accusoft.SmartZoneOCRSdk.SmartZoneException now derives from System.Exception instead of System.ApplicationException. Applications that explicitly catch System.ApplicationException to handle SmartZone exceptions will need updating.

OCR resources are now packaged in folder assets rather than embedding within the assembly. By default, this folder is expected to reside in the same directory as the assembly. However, this folder can be deployed elsewhere and identified at runtime:

IMPORTANT: The path to the OCR resource directory may only use ANSI characters.

Language default character sets have changed. See below for specific changes per character set per language. Apps can edit and define character sets to add characters not presently included for that language with some restrictions.

If you encounter any porting issues, please contact Support for assistance.

Is this page helpful?
Yes No
Thanks for your feedback.