using C# dll in VB6

[ooKmonkey]

Hi

I have an old legacy application that currently uses a c#.net dll for a task. After an update to the dll it is now throwing an Actix x Error (RTE 429) when it tries to use the dll

I have followed the below steps:

• Changes were made to the dll
• Recompiled
• Regasm used to create tlb (and a regfile)
• tlb put onto VB6 dev machine
• Legacy application reference set to use new tlb
• VB6 exe created

Now when I copy the vb6 exe onto my normal dev machine (where the dll was created) it runs fine

When I copy it and the dll onto a target machine (and run the regfile) it gives the RTE 429?

I have created a quick dot.net test app that can use the dll on the target machine without issue

any ideas on what I'm missing? feel like ive been banging my head against a wall for days now

[TysonLPrice]

Long shot...maybe permissions. Are the UAC settings on the machines the same?

Are you going from 32 bit to 64?

[ooKmonkey]

UAC settings are the same as they are set across the board by the IT admins

Just checked on the 32/64 bit and both are the same. (I was hoping you might have been right on that one)

[DEXWERX]

yes, but are you running the regfile as admin?

[ooKmonkey]

I wasn't but have just run it as admin to test.

Registered successfully as before and error still occurs

[TysonLPrice]

I would try:

Remove the reference from the project and close out.
Using regedit delete all the registery entries for the dll.
Add the reference back to the program. I think VB will register it automatically.

[pclement]

Could be a number of reasons for this error. Was the component compiled with a Platform of x86 (32-bit)? Did you add any new dependent libraries outside of the .NET Framework? Have you looked in the Windows Event Log to see if there are any errors related to the app?

[pclement]

Just another thought, is the component in the same folder as the app? If not did you use the codebase argument when running Regasm?

[baka]

I would, as I always do, go the reg-less route. I hate registration and manifest. Just use the reg-free solution.

[ooKmonkey]

Hi thanks for the suggestions

I'll check which platform it was compiled for, I have a feeling it will have been both but will check and try setting it to x86 specifically

Failing that I will try a full un-referencing and re-referencing of the dll and see if that works.

I do have it running from the same folder as the exe.

Thankagain for all the suggestions, I'm really hoping its the x86 target platform one