Re: Replacement for delphi

Dean Hill wrote:

Rudy Velthuis [TeamB] wrote:

Hmmm... what about Delphi for .NET? No need to learn the language,
no need to learn WinForms, and porting should be a lot easier as
well.

It does sound like quite a drastic move. Perhaps he should start
building his new stuff in C# first and then see how it goes from
there.

Dunno, a complete rewrite is the best way to learn things. <g>
--
Rudy Velthuis [TeamB]

"Man has no right to kill his brother. It is no excuse that he
does so in uniform: he only adds the infamy of servitude to
the crime of murder." -- Percy Bysshe Shelley
.

Relevant Pages

  • Re: Replacement for delphi
    ... Rudy Velthuis [TeamB] wrote: ... need to learn WinForms, and porting should be a lot easier as well. ... It does sound like quite a drastic move. ...
    (borland.public.delphi.non-technical)
  • Re: .NET
    ... >> Yes of course applications rewritten by good programmers using sound ... >> techniques are often better than the legacy code. ... Which explains why WinForms is completely ...
    (borland.public.delphi.non-technical)
  • .Net sound recorder
    ... I need to write a small WinForms application to record some sound in WAV and ... then integrate with another online application. ... component or 3rd party component that will let me record sound. ...
    (microsoft.public.dotnet.general)
  • Re: Another about VB 6 <-> VB.NEt
    ... > It is starting to look more and more as if Borland really did the right ... > thing by porting VCL.NET and not relying solely on Winforms. ... How does VCL.NET make your code more portable for Avalon? ...
    (borland.public.delphi.non-technical)