Is your Perl x64 too?

I had problems with Win32::OLE some time ago because I was trying to use COM 
objects on a Win7 x64 using Perl x86. Later I had problems with Perl x64 
trying to access COM objects registered as 32 bit. Perl only sees registered 
COM objects acordingly - if Perl is x86, then only sees 32 bit objects, if 
Perl is x64 then only sees 64 bit objects.

I had to manually register my 32 bit dll on the COM component manager in 
Windows 7, under the 64 bit components but loading the 32 bit dll.

I basically followed the guide in this link although I didn't do everything 
identical to that example:

http://www.maxmind.com/GeoIP_MSCOM_64bit.pdf


HTH

Francisco



-----Mensaje original----- 
From: Philip Prindeville
Sent: Wednesday, August 22, 2012 4:51 PM
To: ActivePerl@listserv.ActiveState.com
Subject: Known issues with Win32::OLE?

I was originally going to check the list archives before posting, but I get 
a 403 from pipermail on the website, so can't do that.

I'm running ActiveState perl (community version) on Win7-x64 updated, and 
wrote the following simple/stupid test program.

#!/usr/bin/perl -w

use strict;
use warnings;

sub obj_cb($)
{
  my $obj = shift;
  my $class = Win32::OLE->QueryObjectType($obj);
  printf STDERR "%s=>%s\n", $obj, $class;
}

my $count = Win32::OLE->EnumAllObjects(\&obj_cb);

printf STDERR "count=%d\n", $count;

exit 1;

and running it (both as myself and as Administrator) I get:

count=0

Anyone have a simple/stupid program that detects whatever programs are 
present that are manipulable via OLE?

I'm trying to get up to speed on Win32::OLE so I can write some 
test-automation tools to exercise our products' GUIs.

Thanks,

-Philip
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs 

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to