Skip to Content
Former Member
Jun 26, 2013 at 09:22 PM

Calling COM Exposed .NET Assembly methods as OLEObject


I'm prototyping calling a .NET 4.0 assy from PB as a COM object. Eventual goal is to use .NET assy as WCF client to vendor SOAP services. (Unfortunately neither PB Classic not .NET are able to generate proxies to these services).

I started with a real simple HelloPowerBuilder example in order to understand the pieces and how they fit together.

I followed Bruce's .NET 2.0 example and 4.0 example as well as another older example

The steps are (as I did them)

Create the assembly

Make COM visible

Build it

Test with .NET WinForm

Copy assembly to PB app folder

Add to Registry (RegAsm) -- I'm on a 32 bit platform

Here's the registry file -

Write PB test harness code

Life should be good -

But it's not?

What am I missing?

How to diagnose a -3 error?



TheClass.png (14.2 kB)
AssyCOM.png (43.3 kB)
TestHarness.png (27.2 kB)
RegFile.png (47.8 kB)
PBCode.png (32.7 kB)
DIr.png (10.8 kB)
Boo.png (3.7 kB)