The reason we want to do it using the utilities is that we actually want to
allow the converted Ocx's or ActiveX Dll's to be accessible from a tool we
are building. We could use the Vs2005 Ide as you suggest (and in fact what it
generates does work in our tool) but we wanted to be able to handle it
independent of the Vs2005 Ide.
On more general grounds we thought that Tlbimp would make the conversion
straight forward but what it produces (though we may not be using it
properly) will not load either into Vs2005 or our tool.
Any help would be appreciated.
Thanks for replying.
--
John Olbert
(E-Mail Removed)
"Nicholas Paldino [.NET/C# MVP]" wrote:
> John,
>
> Why use the TLBIMP utility at all? Why not just right click on the
> toolbox and configure it to add a new item. In the dialog that comes up,
> select the COM tab, and select the controls you want to include in the
> toolbox. The IDE will handle everything else for you.
>
> Hope this helps.
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - (E-Mail Removed)
>
> "John Olbert" <(E-Mail Removed)> wrote in message
> news:59AC9F18-BAAB-40E3-B490-(E-Mail Removed)...
> >I am trying to use the utility tlbimp to add old ActiveX controls and Ocx's
> > to the Toolbox of Vs2005. I tried to apply the the tlbimp to both the Tlb
> > or
> > Dll or Ocx files. The resulting Dll would not load into the toolbox. I
> > suspect I am missing something fundamental. Note that I tried to add to
> > the
> > Vs2005 toolbox both with the original legacy control registered and not
> > registered. In neither case would it load.
> >
> > Because we do not have access to source code for many of the legacy
> > controls
> > we cannot use IJW under C++. We need to use the tlbimp utility.
> >
> > Appreciate any suggestions.
> > --
> > John Olbert
> >
>
>
>
Similar Threads
