Re: [Mono-list] RE: Support for .NET/COM interoperability

2005-01-05 Thread Andy Satori
Erik is correct, you would absolutely want to use Remoting, not WS's 
for performance reasons.  At my last job I tested this extensively as 
we had COM server objects in VB6 that we didn't have time or resources 
to port.  The WebServices avenue was prettier and easier to deploy, but 
was significantly slower and more vulnerable to scalability issues.

Andy
On Jan 4, 2005, at 9:33 AM, Erik Dasque wrote:
On Jan 4, 2005, at 7:16 AM, Jonathan Pryor wrote:

There is an alternate approach, though: Leave your COM code on 
Windows,
and write a .NET front-end which uses .NET COM Interop to use your COM
objects.  The front-end could be an XML Web Service or a
System.Runtime.Remoting server, both of which Mono can communicate 
with.

Thus you'd have:
Mono/Linux -- [Network] -- .NET Web Service -- COM Component
This is likely the easiest approach, though its performance won't be
spectacular.
 - Jon
Yes, I think that's the best option though you might want to use 
remoting instead of WS in that case.

Erik
___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list


Re: [Mono-list] RE: Support for .NET/COM interoperability

2005-01-04 Thread Jonathan Pryor
On Mon, 2005-01-03 at 16:54 +, Robik, Scott wrote:
 If I understand your response correctly, in order to access COM
 calculators that I currently have, I would also need to be running the
 COM runtime on the UNIX host.

Maybe.  See below.

 If this is true then it sound like my only option would be to port the
 calculators to UNIX. I was looking to use MONO as a cross platform
 bridge to allow me to get to these COM servers without having to port
 them to UNIX. Are there any vendors providing COM on UNIX that your
 aware of?

If you need a COM Runtime for Unix, Software AG provides one:

http://www1.softwareag.com/Corporate/products/entirex/downloads/download_exxdcom.asp

However, Mono doesn't provide *any* COM integration, on Windows or Unix,
so this wouldn't allow you to use Mono.

There is an alternate approach, though: Leave your COM code on Windows,
and write a .NET front-end which uses .NET COM Interop to use your COM
objects.  The front-end could be an XML Web Service or a
System.Runtime.Remoting server, both of which Mono can communicate with.

Thus you'd have:

Mono/Linux -- [Network] -- .NET Web Service -- COM Component

This is likely the easiest approach, though its performance won't be
spectacular.

 - Jon

 Regards,
 Scott L. Robik
 
 -Original Message-
 From: Erik Dasque [mailto:[EMAIL PROTECTED]
 Sent: Monday, January 03, 2005 11:41 AM
 To: Robik, Scott
 Subject: Re: Support for .NET/COM interoperability
 
 
 No we do not. There is no reliable COM implementation on UNIX to  
 interface with.
 
 Erik
 
 On Dec 13, 2004, at 2:53 PM, Robik, Scott wrote:
 
  To whom it may concern,
   
  I'm mostly interested in building large scale server side numerical  
  applications. We have a very extensive set of calculators for valuing  
  financial securities and computing various risk scenarios that are all  
  written using COM. I'm very interested in using these on LINUX. Does  
  Mono support the System.Runtime.InteropServices namespace?
 
   
 
  Scott L. Robik
 
  Securities IT
 
 
   Credit Suisse First Boston
  One Madison Avenue
  New York, NY. 10010
 
  ( (212) 538-0165
 
  * [EMAIL PROTECTED]
 
  image.tiff 
 
  === 
  ===
   This message is for the sole use of the intended recipient. If you  
  received this message in error please delete it and notify us. If this  
  message was misdirected, CSFB does not waive any confidentiality or  
  privilege. CSFB retains and monitors electronic communications sent  
  through its network. Instructions transmitted over this system are not  
  binding on CSFB until they are confirmed by us. Message transmission  
  is not guaranteed to be secure.

  === 
  ===
 
  CSFB a1.gif
 
 ==
 This message is for the sole use of the intended recipient. If you received 
 this message in error please delete it and notify us. If this message was 
 misdirected, CSFB does not waive any confidentiality or privilege. CSFB 
 retains and monitors electronic communications sent through its network. 
 Instructions transmitted over this system are not binding on CSFB until they 
 are confirmed by us. Message transmission is not guaranteed to be secure.
 ==
 
 ___
 Mono-list maillist  -  Mono-list@lists.ximian.com
 http://lists.ximian.com/mailman/listinfo/mono-list

___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list


Re: [Mono-list] RE: Support for .NET/COM interoperability

2005-01-04 Thread Erik Dasque
On Jan 4, 2005, at 7:16 AM, Jonathan Pryor wrote:

There is an alternate approach, though: Leave your COM code on Windows,
and write a .NET front-end which uses .NET COM Interop to use your COM
objects.  The front-end could be an XML Web Service or a
System.Runtime.Remoting server, both of which Mono can communicate 
with.

Thus you'd have:
Mono/Linux -- [Network] -- .NET Web Service -- COM Component
This is likely the easiest approach, though its performance won't be
spectacular.
 - Jon
Yes, I think that's the best option though you might want to use 
remoting instead of WS in that case.

Erik
___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list