Type Libraries, 3des encryption

[coloboxp]

Hi,

To implement the 3des encryption, we have used your great library vbCorLib, due to several problems what we are facing we would like to try implementing the type library on VB in order to not have to import them from the .tlb file (also with the vb6 virtual machine tlb). We don’t know too much about VB as you can see, and that is why we think this can help.

Or maybe… do you have a snippet or you know how to do the 3DES encryption like this library does (like .NET) but whitout all the other corlib classes?, also if its possible whitout need to use the Michel Rutten's type lib?

I really hope you can help me.

Thank you very much in advance

[Kelly Ethridge]

Hello,

Since you are talking about the tlb files, it sounds like you are trying to compile the VBCorLib source code yourself. If that is the case and you are having trouble compiling then you can always just use the already compiled version on Source Forge at sourceforge.net/projects/vbcorlib.

However, if you already have a compiled version then you no longer need to keep the tlb file around.

As far as stripping stuff out of the library, that is something that was never planned. Everything depends on everything else. If you are just looking for a VB6 implementation of 3DES, I'm sure there are plenty of them around.

Kelly

[coloboxp]

Hi Kelly, thank you for your answer.

As you said, we are trying to compile your DLL but it is integrated with our own component (our classes togeter with yours), he have allready stripped out a lot of classes and hide them to make the DLL expose our classes only. In fact the size of the DLL was 4.3 MB before and now it is 1.7.

The main reason to do this is because in the planned environment there are not enough privileges to register new DLLS like the vbCorLib one, ours is using binary compatibility to ensure it will be just an overwrite of the old version with this new. (requirements from the customers)

We found allready a lot of implementations of the 3DES alg. but to be honest we couldnt make it work with our services in .NET (we made it compatible with Java allready), thats why your lib came to the rescue.

Also, we are facing problems with the binary compatibility thats why we are attempting to fix it and looking if this can be making problems.

thank you!

[Kelly Ethridge]

Hello,

I understand your situation now. Unfortunately my classes rely on those tlb files when compiling. I can't see why you can't use the tlb files on your development machines when building your DLL. Unless there are duplicate API declarations between the tlb and your DLL. I do provide the tlb source, so you can always remove any duplicates. Almost everything in the VBCorType.tlb should be able to be declared within your DLL instead. However, the VB6 Virtual Machine tlb can't be done so easily. So if the VBCorLib classes you imported into your DLL can use API's declared within your DLL, then you should be good to go, however, I fear that won't be the case. Once you've compiled your DLL you won't need those tlb's anymore.

Kelly