Re: COM Servers

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Are your clients specifying COM? If they are using .NET languages, you can use .NET assemblies (no interop hit), and if they are using an old version of VB or C++, they can use interop (VB6 users have no right to complain about performance, anyway!). Current versions of Delphi, AFAIK, are capable of using .NET assemblies native.

Last I messed with Delphi was version 5. COM support was a bit weak back then, maybe it's gotten better since then (setting up things like collection classes for supporting for/each contstructs was painful, stuff like that).

I would imagine that future versions of VS will concentrate more on expanding .NET support, as opposed to COM.




glenn wrote: 
Problem is I would eventually like to get to a single programming language
for this project.  I don't want to have to continue to program in 2
languages and as it stands its starting to look like Delphi might be the
best choice.  It seems to generate much faster code, has a much better IDE
with lots more components, manages code a lot better, and the data access
elements of the language are far better designed and thought out than it
appears have been done in VS2003.  One reason I'm holding off is I want to
see if any of these items have been addressed in VS2005 but I have no idea
how long that wait is going to be.

And it also sounds like the COM elements of it are going to be the same
which means any interfaces I write that I need to share with other companies
are going to run much slower than if written in Delphi.

This is very disappointing...

glenn


"Michael Moreno" <abc@xxxxxxx> wrote in message
news:mn.28fd7d549353009c.26479@xxxxxxxxxx

How much of a performance hit?  I am use to writing my COM servers in
Borland Delphi.  Are my components written in C# going to be drastically
slower?


Here are my thoughts:
1 - You could continue using Delphi to write your COMs
2 - C# + COM => Interop call. This can be very expensive if there are
many many calls!

--

----------------------------------------------

http://michael.moreno.free.fr/




.

Relevant Pages

  • Re: Noun Oriented Thinking Considered Harmful
    ... I like Delphi because it doesn't force me to use classes or interfaces to ... Object Pascal and entirely object-oriented languages like Java and C#. ... again need one or more diagrams - UML diagrams showing inheritance trees, ... programming paradigm introduced in Pascal and perfected in languages like ...
    (borland.public.delphi.non-technical)
  • Re: 64-bit Windows for AMD 64 is here...
    ... and the same went for Delphi vs. VS/win32. ... Delphi has quite a few features other languages don't have. ... But Delphi ports to .NET are a lot ... >> strings or StringBuilders. ...
    (borland.public.delphi.non-technical)
  • Re: Delph Superior to New D Language
    ... There is nothing wrong with discussing other languages, seeing improvements ... and comparing them to Delphi. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi roadmap from the .NET perspective...
    ... If you want to forfeit that choice, by all means use Delphi for .NET. ... Keeping the number of programming languages, frameworks, IDEs, etc, low is vital. ... I know companies that are having a lot of trouble managing only Java frameworks... ...
    (borland.public.delphi.non-technical)
  • Re: Setting based 1 Arrays
    ... The proof of concept was done - a single DLL for all languages that support COM+ and automation. ... Years ago with VS6, I did attempt an ActiveX control so that VS6 developers can just drop a control on a form, etc, and have right click property features. ... "You might want to also look into .NET assemblies. ... Dim user as Tuser ...
    (microsoft.public.dotnet.languages.vb)