|
|
Browse by Tags
All Tags » licensing
-
Hi All,
In our Web application, we are using dotimage4.0 and 6.0 for 32 bit and 64 bit respectively. Currently we are looking for a single version of dotimage which should support both 32 and 64bit platform. We assume that Dot Image 6 & 7 versions does not support both 32 and 64 bit. whereas version 8 would support both platform. Is that ...
-
I am using atalasoft.dotimage, atalasoft.dotimage.lib, atalasoft.dotimage.pdf, atalasoft.dotimage.wincontrols, atalasoft.dotimage.wpf, atalasoft.dottwain, atalasoft.pdfdoc and atalasoft.shared
libraries in my application.
I included the .licx file with
Atalasoft.Imaging.AtalaImage, Atalasoft.dotImage
Atalasoft.Imaging.Wpf.AtalaImageViewer, ...
-
How do I add a license file to my DLL when it's a COM component into a software package that I don't have control over?
-
I have a licence to ''DotImage Document Imaging 5.0 SDK'', when i build a new class using Atalasoft.DotTwain i need to use ''Atalasoft.dotTwain.lic'' or can i use the ''Atalasoft.dotImage.lic'' ?
-
When deploying to a client's machine, you do not need to install the SDK. You simply need to copy the referenced .NET assemblies and the GlyphReader dll's to a single folder. If you do this, you'll need to include the GlyphReaderLoader class in a static method of your project per instructions in the documentation ...
-
An OCR and PDF Translator license requires DotImage, so what you request is not feasible. You'll need to purchase an additional server license of DotImage for the second server.
-
When you activate your serial number make sure you are using the Activation utility that is associated with DotImage 3.0, not a newer one. That should create a license file for you that works.
-
You need to make sure that the license file is embedded into the resource. Often Visual Studio will include the correct information in licenses.licx if you use a visual component (such as the DotTwain component) but if you do it all in code, you will need to create this licenses.licx file yourself. The joys of .NET licensing, most ...
|
|
|