CODEWITHSUNDEEP
c#.netvb6
DidIReallyWriteThat
DidIReallyWriteThat

Reputation: 1033

vb6 Is keeping an old reference locked

I created a wrapper class to load CLR4(.net) into CLR2(vb6). It works, sort of.

I compile my program in .net(4.0) and run a batch file to create a .tlb. I refrence the .tlb from my vb6 program and everything is awesome.

When I change the wrapper and redo the above process, vb6 will not see the new .tlb, it still uses the old one.

...Anything?

Upvotes: 0

Views: 127

Answers (2)

kevcoder
kevcoder

Reputation: 955

We have a similiar situation here at work ( a vb6 app hosting .net assemblies).

You want to run REGASM /unregister *.dll. The *.tlb is a product of running REGASM /TLB.

If you have your .net project is registered for COM interop, it should do this for you at ever build.

Upvotes: 1

Jeremy
Jeremy

Reputation: 4838

Try to un-register the old tlb before deploying the new one. Open a cmd shell and type "regsvr32 /u mytlb.tlb", then deploy the new, and run regsvr32 again without the /u switch.

see https://technet.microsoft.com/en-us/library/bb490985.aspx for additional information.

Upvotes: 1

Related Questions