Re: Register TLB

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Jojo" <Jojo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:68E12D29-25E5-4A0F-AA3F-6C6C2B8BC9F2@xxxxxxxxxxxxxxxx
I also have a similar problem, where I have created a VB.net .dll and
associatred .tlb files to be used by a vb6 application. I can reference
the
.tlb file in the vb6 application and all works well on the development
machine. But I get the error 429 on the deployed machines.

Looking at the set-up files, the .tlb file is self-registered, but I guess
the problem might in its inability to find the associated .dll file. The
..dll
file was originally missing from the set-up list and I have now included
it
into the apps directory. This should have been done automatically by the
PackageDeploymentWizard in vb6, if only it could understand the
dependencies
of the .tlb file.

There didn't seem an option for generating a dependency file in vb.net ,
nor
a way to inform vb6's PDW to make use of it. Any clues?

Is there a way of forcing PDW to incorporate the .dll in such a way as to
sort out this deployment problem on other machines ?

Many Thanks

Jojo

<snipped>

From VB6's view a typelib is only used by the development environment it
should never be distributed with a compiled application. When you create a
Dll in VB6 the typelib, for that Dll, is included within the Dll. You can do
the same in .net.

(Still not too clear what the problem is here. Are you attempting to include
dotNet components with in a P&D package?)

As for the P&D Wizard.
1) You can use it to create .def files for components.
P&D "Package Type" dialog.
(.def files are simple text file so you can also create your own. Locate
one or two on your development box and open it up.)
2) If there are .def files associated with your components P&D will pick
them up. If not then it makes a good guess...
3) The P&D Wizard will pick up immediate dependancy (as shown with dumpbin)
buts doesn't always "walk" the library list. (A.dll uses B.dll which uses
C.dll, ...). If you have such a component it is usually best to have the P&D
create a dependancy file and then check it for included components.
4) When using the P&D Wizard you are presented with the "Included Files"
files dialog. You should check this to make sure it picked up all the
components and add and remove as appropriate. Add other files here.

hth
-ralph


.

Relevant Pages

  • Re: C# DLL is throwing Automation Errors on some machines when cal
    ... This applies for the COM+ and COM Interop examples. ... example DLL and called it from the Excel VBA application as I had ... new VB6 application. ... come COM Interop from VBA works on a the majority of machines (such as ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Register TLB
    ... The .net DLL was created and compiled with the "COM visible" option, ... Although the .DLL file appeared to be also registered, vb6 refused to ... So, I am left with having to reference the .TLB file, ... There didn't seem an option for generating a dependency file in vb.net, ...
    (microsoft.public.vb.general.discussion)
  • Re: C# DLL is throwing Automation Errors on some machines when called from VB6
    ... This applies for the COM+ and COM Interop examples. ... example DLL and called it from the Excel VBA application as I had ... new VB6 application. ... come COM Interop from VBA works on a the majority of machines (such as ...
    (microsoft.public.dotnet.framework.interop)
  • Casting Problem
    ... I now try to use reflexion to create an object from VB6 DLL to .NET ... I've tried running it on 2 machines both are XP ... is a casting error on 1 of machine and other one works fine. ...
    (microsoft.public.dotnet.framework.interop)
  • RegAsm.exe missing from client machines
    ... I've developed a VB6 application that uses a VB.Net dll. ... distributed to client machines it works fine except for a few cases. ... The clients having problems seem to be missing RegAsm.exe from their ...
    (microsoft.public.dotnet.languages.vb)