Re^2: DLL or VB to Perl

I have made VBS:

Set objLib = CreateObject("CortalConsors.TradingAPI.VersionInfo")
name = objLib.GetAssemblyFullname() 
MsgBox name
[download]

The VBScript Converter translate this:

#!perl
use Win32;
use Win32::OLE;
$objLib = Win32::OLE->new('CortalConsors.TradingAPI.VersionInfo');
#### Error: Can't resolve progID CortalConsors.TradingAPI.VersionInfo
$name = $objLib->GetAssemblyFullname();
Win32::MsgBox($name);
[download]

The VBScript work fine --> The perl not !!

I have install "SystemScripter" --> This tell me (If I want load the

COM-Object 'CortalConsors.TradingAPI.VersionInfo'):"Typelibrary Missing"

and can not resolve the details from COM.

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

Both (DLL and TLB) are in registry --> maybe not right !?

What can I do in perl ???

Comment on Re^2: DLL or VB to Perl Select or Download Code

Replies are listed 'Best First'.
Re^3: DLL or VB to Perl by Anonymous Monk on Jun 16, 2014 at 19:33 UTC
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?	[reply]
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.` [download] In which manner can I do this in perl ??	[reply] [d/l]
Re^5: DLL or VB to Perl by Anonymous Monk on Jun 18, 2014 at 08:10 UTC
Don't give up :) maybe Re^2: Calling .NET Assemblies with Win32::OLE is helpful, but see below for "advice" I have in "SystemScripter... Thats great but SystemScripter is not an API documented on MSDN :) ... In which manner can I do this in perl ?? See Re^3: DLL or VB to Perl, seek out the API calls you need on MSDN, then find them in Win32::OLE... or Win32::API Sorry, thats the way win32 works, the knowledge is on MSDN ... whether you're doing it "in perl" or whatever language, the knowledge is on msdn See for yourself https://metacpan.org/source/JDB/Win32-OLE-0.1712/OLE.xs ... its all CLSIDFromProgID ... CLSIDFromString ... CLSIDFromRemoteRegistry ... CoCreateInstance CLSIDFromProgID function (COM), CLSIDFromString function (COM), Defining COM Interfaces (COM)... It seems to me you have to get the ids into the registry somehow ... So if the above isn't working, well, then get a better error message, something you can find info on MSDN :/ more generic win32 tips Read more... (2 kB)	[reply]

The VBScript work fine --> The perl not !!

What can I do in perl ???

In which manner can I do this in perl ??