LEADTools DLLs not being registered when referencing a ".CAB" file in an ASP.NET web page

I apologise in advance if this question has been asked and answered before.  I've searched the forums and have found similar questions, but not the exact answer that I need.  I'll also apologise if I've posted this question in the wrong forum!

I work for a software company and we are in the process of developing a new ASP.NET web application. It needs to provide a facility whereby the remote user (who has none of the LEADtools software installed), will visit one of our web pages, be able to scan documents using a scanner attached to their PC, view the image and then upload them to a database on our web server.

I downloaded the full evaluation version of LEADtools yesterday and have been looking into what is required to achieve this.

We already use the LEADTOOLS Raster Imaging PRO for .NET tools to provide scanning capabilities within another VB.NET application which we developed a short while ago.

I've created a very simple VB6 ActiveX control with a scan button and a raster viewer control. I can run this within Microsoft Visual Basic 6 and it fires a web page and runs the control.  I can then click scan and the scanner scans!

I've then built this to an ".ocx" file and using the "Package and Deployment Wizard", created a "CAB" file, which appears to contain the necessary Leadtools Dlls and the ".INF" file, the content of which I've included below.

I've then built a very simple single page ASP.NET web application referencing the ".OCX" (I've added it to the toolbox and added it as a reference, which resulted in LTRASTERIOLib, LTRASTERLib, LTRASTERMRCLib, LTRASTERTWAINLib and LTRASTERVARIANTLib also being added as references).

If I run this web page on my PC, then the control appears although IE 6 (Windows XP SP2) complains that the OCX is unsafe (presumably because I haven't managed to sign the OCX yet).

If I use another PC in the office to access this web page on my PC, then it prompts me to install the ActiveX, it seems to go through the motions (the first time I did this it even needed to reboot, presumably because it had installed some VB6 runtime components), but then it doesn't seem to install the necessary Leadtools DLLs and naturally the OCX simply displays a red cross in the corner.

I've searched the other PC looking for the Leadtools DLLs which I think should have been installed in "Windows\System32", but cannot find them.

Sorry for the wordy, lengthy post but I'm a bit stuck as to where I can go from here.

Is there something I'm not doing correctly? I realise that I haven't managed to sign the OCX yet (I did download the lpktool from Microsoft to try and generate a test key, but with little success).

I can't understand why the leadtools DLLS are not installing on the other PC, when the VB6 runtime ones did seem to install.

Any help anyone could provide would be greatly appreciated.

I have read through the various sections in the help files installed with the evaluation version of the Leadtools product and also trawled many, many web sites and forums to try and find out what I'm doing wrong, but with no success!!

Many thanks in advance

Guy

 

;INF file for ScanningTest.ocx
;DestDir can be 10 for Windows directory, 11 for Windows\System(32) directory, or left blank for the Occache directory.

[version]
signature="$CHICAGO$"
AdvancedINF=2.0

[DefaultInstall]
CopyFiles=install.files
RegisterOCXs=RegisterFiles

[RInstallApplicationFiles]
CopyFiles=install.files
RegisterOCXs=RegisterFiles
[DestinationDirs]
install.files=11

[SourceDisksNames]
1=%DiskName%,ScanningTest.CAB,1

[Add.Code]
ScanningTest.ocx=ScanningTest.ocx
ltnet14E.ocx=ltnet14E.ocx
LTRCVW14e.DLL=LTRCVW14e.DLL
LTRVW14e.OCX=LTRVW14e.OCX
LTRVR14e.dll=LTRVR14e.dll
LTRTN14e.DLL=LTRTN14e.DLL
LTRIO14e.DLL=LTRIO14e.DLL
LTR14E.DLL=LTR14E.DLL
ltocx14E.ocx=ltocx14E.ocx
MSVBVM60.DLL=MSVBVM60.DLL
OLEAUT32.DLL=OLEAUT32.DLL
OLEPRO32.DLL=OLEPRO32.DLL
ASYCFILT.DLL=ASYCFILT.DLL
STDOLE2.TLB=STDOLE2.TLB
COMCAT.DLL=COMCAT.DLL

[install.files]
ScanningTest.ocx=ScanningTest.ocx
ltnet14E.ocx=ltnet14E.ocx
LTRCVW14e.DLL=LTRCVW14e.DLL
LTRVW14e.OCX=LTRVW14e.OCX
LTRVR14e.dll=LTRVR14e.dll
LTRTN14e.DLL=LTRTN14e.DLL
LTRIO14e.DLL=LTRIO14e.DLL
LTR14E.DLL=LTR14E.DLL
ltocx14E.ocx=ltocx14E.ocx

[SourceDisksFiles]
ScanningTest.ocx=1
ltnet14E.ocx=1
LTRCVW14e.DLL=1
LTRVW14e.OCX=1
LTRVR14e.dll=1
LTRTN14e.DLL=1
LTRIO14e.DLL=1
LTR14E.DLL=1
ltocx14E.ocx=1

[ScanningTest.ocx]
file-win32-x86=thiscab
RegisterServer=yes
DestDir=
FileVersion=1,0,0,1

[ltnet14E.ocx]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140030-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[LTRCVW14e.DLL]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140D12-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[LTRVW14e.OCX]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140708-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[LTRVR14e.dll]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140B9B-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[LTRTN14e.DLL]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140752-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[LTRIO14e.DLL]
file-win32-x86=thiscab
RegisterServer=yes
clsid={001408A2-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[LTR14E.DLL]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140705-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[ltocx14E.ocx]
file-win32-x86=thiscab
RegisterServer=yes
clsid={00140007-B1BA-11CE-ABC6-F5B2E79D9E3F}
DestDir=11
FileVersion=14,5,0,5

[MSVBVM60.DLL]
hook=MSVBVM60.cab_Installer
FileVersion=6,0,97,82

[MSVBVM60.cab_Installer]
file-win32-x86=http://activex.microsoft.com/controls/vb6/VBRun60.cab
run=%EXTRACT_DIR%\VBRun60.exe

[OLEAUT32.DLL]
hook=OLEAUT32.cab_Installer
FileVersion=2,40,4275,1

[OLEAUT32.cab_Installer]
file-win32-x86=http://activex.microsoft.com/controls/vb6/VBRun60.cab
run=%EXTRACT_DIR%\VBRun60.exe

[OLEPRO32.DLL]
hook=OLEPRO32.cab_Installer
FileVersion=5,0,4275,1

[OLEPRO32.cab_Installer]
file-win32-x86=http://activex.microsoft.com/controls/vb6/VBRun60.cab
run=%EXTRACT_DIR%\VBRun60.exe

[ASYCFILT.DLL]
hook=ASYCFILT.cab_Installer
FileVersion=2,40,4275,1

[ASYCFILT.cab_Installer]
file-win32-x86=http://activex.microsoft.com/controls/vb6/VBRun60.cab
run=%EXTRACT_DIR%\VBRun60.exe

[STDOLE2.TLB]
hook=STDOLE2.cab_Installer
FileVersion=2,40,4275,1

[STDOLE2.cab_Installer]
file-win32-x86=http://activex.microsoft.com/controls/vb6/VBRun60.cab
run=%EXTRACT_DIR%\VBRun60.exe

[COMCAT.DLL]
hook=COMCAT.cab_Installer
FileVersion=4,71,1460,1

[COMCAT.cab_Installer]
file-win32-x86=http://activex.microsoft.com/controls/vb6/VBRun60.cab
run=%EXTRACT_DIR%\VBRun60.exe

[RegisterFiles]
%11%\ltocx14E.ocx
%11%\LTR14E.DLL
%11%\LTRIO14e.DLL
%11%\LTRTN14e.DLL
%11%\LTRVR14e.dll
%11%\LTRVW14e.OCX
%11%\LTRCVW14e.DLL
%11%\ltnet14E.ocx
%11%\ScanningTest.ocx

Guy,
The LEADTOOLS files listed in your INF file can be classified into 4 groups:
1. Main OCX and 'dynamic' files:
ltocx14E.ocx
ltnet14E.ocx

2. Raster COM and 'static' files:
LTRVW14e.OCX
LTRTN14e.DLL
LTRIO14e.DLL
LTR14E.DLL

3. Supporting (used with both group 1 and 2):
LTRVR14e.dll

4. Other:
LTRCVW14e.DLL

About groups 1 and 2:

Normally, you should use either group 1 or 2, but not both in the same
application. The functionality of the main OCX (LTOCX) exists in
different Raster COM objects and controls. For example, the main OCX
contains functions for loading and saving images, which also exist in
the RasterIO object (LTRIO). Also, LTOCX has image display features which exist in RasterView (LTRVW) and so on.

About 3:

This is the LEAD Raster Variant object, which is used by TWAIN and some other objects. It is used with both LTOCX and LTR???? objects.

About 4:

LTRCVW is the LEADTOOLS Image Viewer COM Object. This is an almost
independent object (part of LEADTOOLS Medical Imaging Suite toolkit) and used for displaying DICOM and medical images.


After you decide which group you want to use (LTOCX or LTR???), read
the help topic "Files to be Included with Your Application" if you
haven't done so already. It explains which files are needed for which features.

The topic to read will be either in the Main OCX help file, or the main Raster COM help file, based on which of the 2 groups you decide to use.


For example, to register the main OCX (LTOCX14E.OCX) you need its list
of dependency files in the same folder. As a minimum, the following files are needed to register it:
LTDIS14E.DLL
LTEFX14E.DLL
LTFIL14E.DLL
LTIMG14E.DLL
LTKRN14E.DLL

I have a similar problem with our application not working on some computers and giving a VB6 run time error when rolling the mouse over the LEADRast1 control.

Can you tell me specifically where to find the help files that explain which files to distribute with the application? I don't see it in any of the LeadTools subfolders on my system.

Thank you,
Glen

Glen,

There is
a different version of the help topic "Files to be Included with Your
Application" in every main LEADTOOLS help file, and also in smaller help
files for different toolkit features, such as the Barcode help files and the Twain help files.

If the
LEADRast1 control you're referring to is a LEAD Raster View COM control, you
should find the relevant "Files to be included.." topic in the Main Raster COM objects help file.

About the error you're getting, what does your code do exactly in the Mouse Move event handler?