W
Wilbur Slice
I need to write some VB.NET objects that can be called from another
environment (a Progress app, specifically). I'm having some
difficulty getting this to work.
My first assumption was that I should write a COM object. Is this a
good approach? Or is there a better one?
I wrote the new VB.NET object and included a COM Class object. All is
fine and the system creates a TLB file and everything. It all works
great on my development machine. But when I try to deploy it to the
target (XP-PRO) machine and write a test subroutine in Word using VBA
to access the object, I fail. It works in VBA on my development
machine, but not on the machine I'm deploying to.
First, I can't see my COM object when I try to add a reference in VBA.
So I use regasm.exe to register the COM object DLL - it reports
success. But my COM object still doesn't show up in Word VBA's list
of COM objects that I can reference. But when I do a "browse", I can
see it, and the TLB file. I can't reference the DLL, but I *can*
reference the TLB.
And then VBA knows about my COM object and I can add it to my VBA code
(intellisense works and everything). But then when I run the VBA
subroutine, when it tries to run a function from my VBA object I get
an error saying "File or assembly name MKRCOM, or one of its
dependencies, was not found."
Does anybody know what I need to do? Or can anyone point me to a
resource that describes how to develop COM objects under VB.NET that
can be called by non -.NET programs?
Thanks in advance...
environment (a Progress app, specifically). I'm having some
difficulty getting this to work.
My first assumption was that I should write a COM object. Is this a
good approach? Or is there a better one?
I wrote the new VB.NET object and included a COM Class object. All is
fine and the system creates a TLB file and everything. It all works
great on my development machine. But when I try to deploy it to the
target (XP-PRO) machine and write a test subroutine in Word using VBA
to access the object, I fail. It works in VBA on my development
machine, but not on the machine I'm deploying to.
First, I can't see my COM object when I try to add a reference in VBA.
So I use regasm.exe to register the COM object DLL - it reports
success. But my COM object still doesn't show up in Word VBA's list
of COM objects that I can reference. But when I do a "browse", I can
see it, and the TLB file. I can't reference the DLL, but I *can*
reference the TLB.
And then VBA knows about my COM object and I can add it to my VBA code
(intellisense works and everything). But then when I run the VBA
subroutine, when it tries to run a function from my VBA object I get
an error saying "File or assembly name MKRCOM, or one of its
dependencies, was not found."
Does anybody know what I need to do? Or can anyone point me to a
resource that describes how to develop COM objects under VB.NET that
can be called by non -.NET programs?
Thanks in advance...