NOTE: this article refers to our .NET Imaging SDKs (DotImage, DotTwain, WingScan, and

DotPdf)

Background

When you upgrade to a new version of DotImage - be that to the next hotfix or fixpack or

even when upgrading after having skipped multiple releases, there are a few steps here that

should help ensure you get a successful update.

Procedure

Install the SDK and Activate Updated Licenses (if

needed)

First, you will need to ensure you've installed the new version of the SDK on your

sometimes that download page lags behind the latest - if we have just released a new

update, and it's not "live" there yet, you may need to create a support case to ask for it.

Also note that our NuGet packages take up to 2 weeks to "go live" after a new version is

released - unfortunately while support can get you the certified SDK installer as soon as the

release has been certified by QA, the NuGet publish process has no shortcut/workaround -

so users using that method to get our packages will have to wait until their needed version

is live.

When Licenses Need Updating

When you activate a license you will be activating for a specific MAJOR.MINOR.. so

DotImage 9.0 to 10.0 was a MAJOR version as would be 10.0 to 11.0 etc.. but what you

service packs, fixpacks and hotfixes).

Lets say you're on 11.3.0.3.730 and lets say you're updating to a new fixpack but it's still

11.3 - so 11.3.0.4.742 (the final 11.3 release we made)

This would NOT require a new license if you're already licensed for 11.3

2) Upgrade required

Now, instead lets say you're on 11.3.0.4.742 and you need to move to an 11.4 release. The

latest (as of October 2022) is 11.4.0.3.311 which is 11.4, Fixpack 3.

This would require new license FILES but you don't need to go get new licenses or contact

sales - so long as you're under maintenance, you just need to activate your existing serials

for 11.4.

HOWTO: Activate DotImage SDK or Server (Including Offline Activation)

NOTE: this needs to be applied to all projects within the solution as you can not mix

versions of DotImage in the same solution (or in the same project)

When you install the new SDK, if you're moving in the same MAJOR.MINOR (so say going

from one 11.3 release to a newer one that is still under 11.3, then the install OVERWRITES

the previous version. However, when going up to a new MAJOR.MINOR such as moving from

11.3.x.y.zzz to 11.4.x.y.zzzz then the old 11.3 will not be touched - the install will happen

and the new version will end up in its own Program Files directory - so for 11.3 it would be

in C:\Program Files (x86)\Atalasoft\DotImage 11.3\ and the 11.4 would install to

C:\Program Files (x86)\Atalasoft\DotImage 11.4\. Likewise, as mentioned above with new

licenses, your license files end up in their own directory separated by version so when you

activate an 11.4 license it will leave your 11.3 ones alone and overwrite any previous 11.4

licenses (which can be found in its default location - please see FAQ:Where Can I Find My

at the new version.

Another way to update is to manually edit your csproj / vbproj project file to change the hint

paths

So, if you edit your csproj / vbproj file, look for the Atalasoft related items

Current Project File (partial):

ItemGroup> <Reference Include="Atalasoft.dotImage"> <Name>Atalasoft.dotImage</Name>

<HintPath>C:\Program Files (x86)\Atalasoft\DotImage

11.3\bin\4.5.2\x86\Atalasoft.dotImage.dll</HintPath> </Reference> <Reference

Include="Atalasoft.dotImage.Lib"> <Name>Atalasoft.dotImage.Lib</Name> <HintPath>C:\Program

Files (x86)\Atalasoft\DotImage 11.3\bin\4.5.2\x86\Atalasoft.dotImage.Lib.dll</HintPath>

11.4\bin\4.5.2\x86\Atalasoft.dotImage.dll</HintPath> </Reference> <Reference

Include="Atalasoft.dotImage.Lib"> <Name>Atalasoft.dotImage.Lib</Name> <HintPath>C:\Program

Files (x86)\Atalasoft\DotImage 11.4\bin\4.5.2\x86\Atalasoft.dotImage.Lib.dll</HintPath>

</Reference> <Reference Include="Atalasoft.Shared"> <Name>Atalasoft.Shared</Name>

<HintPath>C:\Program Files (x86)\Atalasoft\DotImage

11.4\bin\4.5.2\x86\Atalasoft.Shared.dll</HintPath> </Reference> ... </ItemGroup>

If it's still not "sticking" make sure you don't have a "reference paths" set. To check this:

• Go to Visual Studio Solution Explorer

• Right click on the project

• select "Properties"

This is also useful for quickly switching versions without having to edit the csproj file - just

switch which one is on top and check that your references are updated.

Remember to save the solution and rebuild the project for the new versions to be used.

ON NO ACCOUNT should you mix different versions of Atalasoft DLLs in the same project

or even in different projects in the same solution - you can have multiple versions of

DotImage in different solutions but do not mix them in the same project.

WebDocViewer Resources

If you're using our WebDocumentViewer and/or WebDocumentThumbnailer in your app, you

need to update your WebDocViewer Resources, and verify if there are changes needed to

the script version links.

(x86)\Atalasoft\DotImage 11.4\bin\WebResources\WebDocViewer\

talaWebDocumentViewer.css atalaWebDocumentViewer.d.ts atalaWebDocumentViewer.js

clipboard.min.js jquery-3.5.1.min.js jquery-ui-1.13.1.min.css jquery-ui-1.13.1.min.js

raphael-min.js images\atala-ui-dragdropfile.png images\atala-ui-icons-16.png

images\atala-ui-spinner.gif images\ui-icons_444444_256x240.png

images\ui-icons_555555_256x240.png images\ui-icons_777620_256x240.png

images\ui-icons_777777_256x240.png images\ui-icons_cc0000_256x240.png

images\ui-icons_ffffff_256x240.png

What you want to do is replace the current ones in your solution with the ones from the

update

WebCapture Resources

If you're using our WebCapture (WingScan) components, then when updating to a new

version, you need to update/replace all the WebCapture Resource files in your solution with

the new ones

NOTE: they will have the same file names so it's critical to not assume they're unchanged -

you MUST update

TO do this, you need to find the files in your solution that correspond to the WebCapture

Resource files provided in our SDK.

Version 11.4 shipped with the following contents of C:\Program Files

(x86)\Atalasoft\DotImage 11.4\bin\WebResources\WebCapture\

talaWebCapture.js Kofax.WebCapture.Installer.msi Kofax.WebCapture.macOS.pkg

Script Dependencies

This was already somewhat covered above but we need to be explicit about it here...

We update our scripts every time and don't list versions in file names so in theory if you

have updated the scripts underneath, then you don't need to change the links in your

markup, but when the version of jQuery and jQueryUI update, we need to also be sure

we're pointing to the right ones...

Example:

in 11.3.0.3, we changed from jQueryUI 1.12.1 to 1.13.1. So, the new files shipped will

include

jquery-ui-1.13.1.min.js

!-- Js scripts in correct order --> <script src="WebDocViewer/jquery-3.5.1.min.js"

type="text/javascript"></script> <script src="WebDocViewer/jquery-ui-1.12.1.min.js"

type="text/javascript"></script> <script src="WebDocViewer/raphael-min.js"

type="text/javascript"></script> <script src="WebDocViewer/clipboard.min.js"

Additionally, serial numbers changed - very old 7.0a and older barcode serials start with

BRD2,BRP2, or BRS2.

Atalasoft.dotImage.PdfReader.dll