Delphi client / VS 2003 COM Server

[glenn]

I've gotten a COM server written in C# and I can call it from a VBScript
just fine and it works perfectly. However, I import it into Delphi 6 or
Delphi 2005 and I can not get access to any of the functions that are in the
server. Is there something specific that I need to do in order to get
Delphi to see the functions that are a part of the server?

Thanks,

glenn

[Willy Denoyette [MVP]]

"glenn" <gh******@softe ksoftware.com> wrote in message
news:eO******** ******@TK2MSFTN GP10.phx.gbl...

Willy,

- COM Interop Part 1: C# Client Tutorial
- COM Interop Part 2: C# Server Tutorial

I have already reviewed and tried the sample programs that you suggest
here
and they don't work either. In fact they just add to the confusion for me
as they are completely different than what the book on COM gives as
tutorials for this subject. I am convienced that something has to be done
here to expose these functions to other program languages that run in
unmangaged code, however, I do not see how this is to be done yet...

Any help would be appreciated...

glenn

These samples work with VB, C++, VBScript native COM clients, seems like
Delphi has a problem importing the typelib created by regasm.

Willy.

[glenn]

Doug,

Thanks, I'll try that out and see if its my problem. I am also suspecting
Delphi here but just not sure what to do since it has never had a problem
like this before with any other COM server i've used.

Thanks,

glenn
"Doug Forster" <doug_ZAPTHIS_A T_ZAPTHIS_TONIQ _DOT_CO_DOT_NZ> wrote in
message news:eX******** ******@TK2MSFTN GP10.phx.gbl...

Hi Glenn,

Well I have no experience with writing managed COM servers but I had no real problem getting a variation of the sample to work via Delphi 6.
Firstly if you import the type library there is a dependency on mscoree that does not wrap correctly due to Delphi being CI. You can manually modify the wrapper to fix this. If you use the designer to create your client interface object then you must explicitly cast it to your interface to get to the
correct interface or alternatively Philips suggestion using late binding
also works fine, but you might need to scout around the registry to find the class name that VS generates.

These worked:
procedure TForm1.Button1C lick(Sender: TObject);
Var
MyServer: Variant;
Begin
(InterfaceImple mentation1.Defa ultInterface as
IManagedInterfa ce).PrintHi('He llo world');
MyServer := CreateOleObject ('CSharpServer. InterfaceImplem entation');
MyServer.PrintH i('Hello world');
End;

However, this is a must to figure out in order to be able to do this. If I
can not get COM to work properly with .NET in VS then I will be forced to continue to use Delphi 6 for all our solutions.

These problems are only minor as far as I can see.

Cheers
Doug Forster

[glenn]

Doug,

I must be missing something. I've copied your code exactly and also have
the same app setup exactly as the tutorial. However, when I run my delphi
exe, I get no errors, but I also get no results. It just passes over the
line for the COm server and moves on...
(InterfaceImple mentation1.Defa ultInterface as
IManagedInterfa ce).PrintHi('He llo World');

Again, no compile errors and no errors at run time, but no results when
running the above line. I also tried the second method using the variant
but it results in same thing... Any ideas what i might be doing wrong here?

Thanks,

glenn
"Doug Forster" <doug_ZAPTHIS_A T_ZAPTHIS_TONIQ _DOT_CO_DOT_NZ> wrote in
message news:eX******** ******@TK2MSFTN GP10.phx.gbl...

Hi Glenn,

Well I have no experience with writing managed COM servers but I had no real problem getting a variation of the sample to work via Delphi 6.
Firstly if you import the type library there is a dependency on mscoree that does not wrap correctly due to Delphi being CI. You can manually modify the wrapper to fix this. If you use the designer to create your client interface object then you must explicitly cast it to your interface to get to the
correct interface or alternatively Philips suggestion using late binding
also works fine, but you might need to scout around the registry to find the class name that VS generates.

These worked:
procedure TForm1.Button1C lick(Sender: TObject);
Var
MyServer: Variant;
Begin
(InterfaceImple mentation1.Defa ultInterface as
IManagedInterfa ce).PrintHi('He llo world');
MyServer := CreateOleObject ('CSharpServer. InterfaceImplem entation');
MyServer.PrintH i('Hello world');
End;

However, this is a must to figure out in order to be able to do this. If I
can not get COM to work properly with .NET in VS then I will be forced to continue to use Delphi 6 for all our solutions.

These problems are only minor as far as I can see.

Cheers
Doug Forster

[Philip Hristov]

Glenn,

Do it with CreateOleObject .

Philip.

[glenn]

Actually the previous code was working. I just realized that the C# example
was writing to console and I changed it to a messagebox since I'm testing
with a Delphi Win form. its now popping up the messagebox perfectly. I am
very excited now and can start laying out this project. Thanks for all the
help guys...

glenn
"Philip Hristov" <ph********@gma il.com> wrote in message
news:11******** *************@g 14g2000cwa.goog legroups.com...

Glenn,

Do it with CreateOleObject .

Philip.

[Philip Hristov]

Finally :)

Good luck with your project :)

Philip.

[Doug Forster]

Sorry I forgot to mention that thats what I did too.

Cheers
Doug Forster

"glenn" <gh******@softe ksoftware.com> wrote in message
news:uk******** ******@TK2MSFTN GP09.phx.gbl...

Actually the previous code was working. I just realized that the C#
example
was writing to console and I changed it to a messagebox since I'm testing
with a Delphi Win form. its now popping up the messagebox perfectly. I
am
very excited now and can start laying out this project. Thanks for all
the
help guys...

glenn
"Philip Hristov" <ph********@gma il.com> wrote in message
news:11******** *************@g 14g2000cwa.goog legroups.com...

Glenn,

Do it with CreateOleObject .

Philip.