The LEADTOOLS .NET Class Library is designed as a standard .NET Class Library. You should be able to use the LEADTOOLS .NET Class Library with any compiler that supports .NET.

Most of the LEADTOOLS example programs and all of the documented code examples are for Windows programs written in C# and VB.NET.

The LEADTOOLS .NET Class Library ships with a COM Interop wrapper which allows LEADTOOLS .NET Class Libraries to be used in Visual Basic 6.0 (and other development environments that support COM objects).

For more information refer to the following topics:

LEADTOOLS COM Interoperability

Programming with LEADTOOLS COM Interoperability Functions

COM Interoperability - Loading and Displaying an Image

COM Interoperability - Working with Pages

COM Interoperability - Recognizing Pages

COM Interoperability - Working with Recognition Results.

Files to be Included with Your Application

Applications created using LEADTOOLS .NET assemblies are fully compatible with Microsoft ClickOnce technology. ClickOnce, supported under Visual Studio, allows developers to deploy applications easily via a web server, rather than via an installer. This allows for rapid, simple updates by re-publishing the application. The application can be configured so that when run from the client, it will automatically check and download available updates. Refer to MSDN for a ClickOnce tutorial .

When deploying LEADTOOLS SDK applications, remember to add all LEADTOOLS file filter dlls that you plan to support as references. If this is not done, the ClickOnce deployment tool will not deploy them to the client machine. For a list of required file filter dlls, refer to: Files to be Included with Your Application.

See LEADTOOLS Microsoft Click Once Technology for online examples of LEADTOOLS demos published using ClickOnce.

Visual Studio .NET 2005 is a 32 bit application and 32 bit applications cannot load 64 bit assemblies. If you attempt to add a 64 bit LEADTOOLS control (RasterImageViewer, RasterImageList, etc), to the Visual Studio toolbox, Visual Studio will attempt to load the assembly and fail since a 32 bit application is attempting to load a 64 bit assembly.

The solution is to create and add the controls to your form at runtime. When you add a reference in Visual Studio, the assembly is not actually loaded. For this reason, you can add a reference to the 64 bit assembly, write your code, and compile as usual.

The following sample code demonstrates how to create and add the LEADTOOLS RasterImageViewer to your form at runtime.

   
Leadtools.WinForms.RasterImageViewer rasterImageViewer1;
rasterImageViewer1 = new Leadtools.WinForms.RasterImageViewer();
rasterImageViewer1.Location = new Point(10, 10);
rasterImageViewer1.Size = new Size(500, 500);
this.Controls.Add(rasterImageViewer1);

It is not possible to use the nag kernel with ASP.NET because the nag kernel has a dialog box that pops up every time the assembly is loaded. ASP.NET does not allow dialog boxes, just like a Windows Service application. You will have to use the NO NAG version of the kernel when developing an ASP.NET web application. For information on the NO NAG kernel, refer to LEADTOOLS Nag Message.