Re: Thinking Clearly

Dan Barclay wrote:
I'd encourage you to think more in terms of your code library than specific
applications.

In that respect, I don't see much tangible difference between .NET or
Win32 as Interop is a perfectly suitable solution. This is something
..NET has been designed to do: leverage "legacy" code.

But if one leverages VCL.NET it means that that code needs to run in a
fully-trusted environment. It also means that various .NET techniques
cannot be leveraged to full benefit.

IMO, it's a nice quick/dirty porting solution, but not as a permanent
one because it's not the *best* .NET solution at least as it stands now.

While you may have no need for cross platform *applications*, you may want
to create different applications but use the same code.

Sure, and in those cases n-tier solutions or interop are completely
acceptable solutions to me.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: C#Builder 2007(2008)
    ... Delphi developers to leverage ASP.NET to develop web sites. ... applications in the managed space. ...
    (borland.public.delphi.non-technical)
  • Re: Touchy Subject
    ... > for one obvious reason. ... Current Windows is build in unmanaged code, so, ... > managed code directly to machine code, skipping any interop. ... > console applications. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: Touchy Subject
    ... > for one obvious reason. ... Current Windows is build in unmanaged code, so, ... > managed code directly to machine code, skipping any interop. ... > console applications. ...
    (microsoft.public.dotnet.framework)
  • Re: Touchy Subject
    ... > for one obvious reason. ... Current Windows is build in unmanaged code, so, ... > managed code directly to machine code, skipping any interop. ... > console applications. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Touchy Subject
    ... > for one obvious reason. ... Current Windows is build in unmanaged code, so, ... > managed code directly to machine code, skipping any interop. ... > console applications. ...
    (microsoft.public.dotnet.general)