Re: Thinking Clearly

Bob Dawson wrote:
Businesses migrating seem to disagree.

Certainly. Do you agree with every business that does something out
there? ;)

All firehose cursors and OO layer here. Databinding isn't a big deal with
me.

Ok, but that's *you*. How many within the Delphi community are using
your OPF? ;)

I do like the new object-binding stuff, and would like to see that in
the VCL (along with ClientDataSets that could return iterators rather than
having a single current record concept).

Right...but IMO, those are the things that are sacrificed by choosing to
use VCL.NET. It doesn't leverage the things that the .NET framework
enables so there are disadvantages, which provides some validity to my
previous statements.

Why? All of a sudden the application isn't working on Win32? If there
is nothing in .NET that is going to be utilized, why go .NET at all?

The world doesn't begin and end with applications <g>. There are much
stronger arguments for multiple-platform deployable libraries.

Certainly not, but then why is interop such an awful solution? .NET was
designed from day one to be able to interop with all sorts of "legacy" code.

Besides, like I've said before, in leveraging VCL.NET, there are still
security and "legacy" compromises.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • C# Interop Object Security Permissions Problem
    ... object registered with COM interop from a legacy VC++6 MFC application. ... however if I have my service log in using the system account, ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Thinking Clearly
    ... Win32 as Interop is a perfectly suitable solution. ... ..NET has been designed to do: leverage "legacy" code. ... to create different applications but use the same code. ...
    (borland.public.delphi.non-technical)
  • Re: C#Builder 2007(2008)
    ... Winforms third party offerings, ... Leverage the .NET framework ... 3, IMO, is the most likely choice, but interop is a much better solution. ... leverage the .NET framework more completely (via ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... Win32 as Interop is a perfectly suitable solution. ... .NET has been designed to do: leverage "legacy" code. ...
    (borland.public.delphi.non-technical)
  • RE: Calling a method in a object running in windows service
    ... You will have to use COM Interop which provides backwards compatibility to ... let you leverage existing COM components (or new ones for that matter). ...
    (microsoft.public.dotnet.languages.csharp)