http://www.perlmonks.org?node_id=1090063


in reply to Re^2: DLL or VB to Perl
in thread DLL or VB to Perl

In "SystemScripter" can I give the path of TLB by hand and it's work...

What does that mean? What does that mean in terms of API calls? Why don't you try a "class id" instead?

Replies are listed 'Best First'.
Re^4: DLL or VB to Perl
by joago (Initiate) on Jun 18, 2014 at 07:37 UTC
    I have in "SystemScripter" the list of all registered COM-Objects. I can make program lines with drag and drop. With doble click by the COM-Object its open a window with desccription of the object. For my object the "SystemScripter" tell me "the TLB is missing". The new window has 2 lines with empty information for the TLB (CLSID and adress) at the end of window and the next window with the information from inside the COM (class,method,interfaces ...) not work. If I fill the adress line for the TLB by hand then I can open this information and give it to the program lines with drag and drop.

    I have with "class id" the same problem as with the name:the COM can not open and I have no idee in which manner I sold give the CLSID from TLB to perl.

    NEW INFORMATION: If I want add the COM in old SDK then I have:

    No reference on <assembly> could be added. The ActiveX-type library <link to the library> was exported from a .NET-Assembly and cannot be added as a reference. Add, instead, a reference to the .NET-Assembly.

    In which manner can I do this in perl ??