Welcome Guest! To enable all features, please Login or Register.

Notification

Icon
Error

Options
View
Last Go to last post Unread Go to first unread post
#1 Posted : Monday, October 19, 2009 10:34:17 PM(UTC)
vimalviswam

Groups: Registered
Posts: 7


Hi,

 

Scenario:

We are doing a migration from VB 6.0 to VB.NET 3.5 Framework.

 

Issue: We are using Lead tools version 12.1 in the application and when we migrate the code to dot net, the references to the lead tools get added as interop dlls. As a guideline, we should not be referring to interop Dlls.

 

To give an idea on the steps we followed for migration:

1.       Removed the Form using the Lead Tool Controls and all references to lead tools

2.       Migrated the code using the wizard in VS2008

3.       Added the lead tool components to migrated code

4.       But as soon as reference is made to the dlls, Interops are formed of these components which we want to avoid.

 

Kindly help us and let us know how to remove such Interops as ideally such interops should not be used. In case, any further details, please mail us at bijon_panda@infosys.com

 

Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads

Wanna join the discussion? Login to your LEADTOOLS Support accountor Register a new forum account.

#2 Posted : Tuesday, October 20, 2009 5:39:16 AM(UTC)

Basel  
Guest

Groups: Guests
Posts: 3,034

Was thanked: 2 time(s) in 2 post(s)

If you want to use ActiveX (OCX) controls with VB.NET, Visual Studio 2008 will automatically wrap these controls with interop classes.
If you want your code to use native .NET classes, you should not use OCX controls.
Instead, you could use LEADTOOLS 16.5 .NET classes, but their design is completely different from OCX 12.1, and you cannot use an automatic wizard to do the code conversion. You will have to re-write all the code that's related to LEADTOOLS.

If you want to try our .NET classes, download the free evaluation of LEADTOOLS 16.5 from our site before you consider upgrading.

If you prefer to use email support, send your questions to support@leadtools.com

 
#3 Posted : Tuesday, October 20, 2009 8:12:49 PM(UTC)
vimalviswam

Groups: Registered
Posts: 7


Thanks for the update!!

Two more questions on this:

1. We have a licensce for 14.5 version for Lead Tools. It would be great if you can let us know whether this version is compatible in our case of migration from Vb 6 to VB.NET 3.5.

2. If we can use 14.5, do we have to change the design as in LEADTOOLS 16.5 (mentioned be you)

Awaiting your answer.

 
#4 Posted : Wednesday, October 21, 2009 3:12:58 AM(UTC)

Basel  
Guest

Groups: Guests
Posts: 3,034

Was thanked: 2 time(s) in 2 post(s)

LEADTOOLS V14.5 has different controls in different products. For example, LEADTOOLS 14.5 Raster Imaging Pro for .NET contains .NET Classes which are compatible with .NET framework 1.1 and 2.0.
The design of these classes is different from v12.1, but is very similar to the design of v16.5 .NET classes. Of course the latest version has more features.
This means if you use the native .NET classes of 14.5, you will need to re-write your old v12 application.

On the other hand, if you use the ActiveX objects of version 14.5, some of them (but not all) are similar to controls from version 12, but since these are ActiveX (OCX) controls, they will also have interop wrappers generated for them if you use them with Visual Studio .NET.
 
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2020, Yet Another Forum.NET
This page was generated in 0.165 seconds.