SmartZone v6.1 for .NET - Updated
Upgrading from SmartZone OCR 3 to SmartZone OCR 6
Getting Started > Upgrading SmartZone OCR > Upgrading from SmartZone OCR 3 to SmartZone OCR 6

This section describes how to upgrade from SmartZone 3 to SmartZone 6. While generally you'll be able to replace SmartZone 3 with SmartZone 6, 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 ICR assembly.

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

Licensing Changes

The SmartZone runtime licensing scheme has changed completely, but you can replace the existing with at most three lines of code. See Changing to Automatically Reported Runtime Licensing and Changing to Manually Reported Runtime Licensing sections below for runtime licensing code examples.

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

Runtime Changes

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

Performance Changes

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

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

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. In general, all language character sets gain a few characters, with only the Dutch character set losing 14 characters. Apps can edit and define character sets to add characters not presently included for that language with some restrictions.

Changing to Automatically Reported Runtime Licensing

Automatically Reported Runtime requires a license to be installed on the end-user's machine. See the Licensing section for more information.

In your SmartZone OCR 3 codebase, replace the UnlockRuntime method with calls to the SetSolutionName and SetSolutionKey methods.

smartzoneOCR1.Licensing.SetSolutionName("YourSolutionName");
smartzoneOCR1.Licensing.SetSolutionKey(12345,12345,12345,12345);
smartzoneOCR1.Licensing.SetSolutionName("YourSolutionName")
smartzoneOCR1.Licensing.SetSolutionKey(12345,12345,12345,12345)

Changing to Manually Reported Runtime Licensing

In your SmartZone OCR 3 or later codebase, replace the UnlockRuntime method with calls to the SetSolutionName, SetSolutionKey, and SetOEMLicenseKey methods.

smartzoneOCR1.Licensing.SetSolutionName("YourSolutionName");
smartzoneOCR1.Licensing.SetSolutionKey(12345,12345,12345,12345);
smartzoneOCR1.Licensing.SetOEMLicenseKey("2.0.AStringForOEMLicensing…");
smartzoneOCR1.Licensing.SetSolutionName("YourSolutionName")
smartzoneOCR1.Licensing.SetSolutionKey(12345,12345,12345,12345)
smartzoneOCR1.Licensing.SetOEMLicenseKey("2.0.AStringForOEMLicensing…")

There is no longer a separate method for web licensing. That functionality has been integrated into the SetOEMLicenseKey method.

 

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

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

 

 

©2021. Accusoft Corporation. All Rights Reserved.

Get Product Support