Re: Is there any hope for Microsoft ?




Winforms 1.1 dead
Winforms 2.0 ???

Agreed, but:

VCL 1.0 dead
VCL 2.0 dead
...
VCL 2005 dead:
VCL 2006 ???


I'm still successfully using the original (???) VCL, since it does what I
need.
However, we've wasted a lot of time on Winforms 1.1, to get around the
limitations on things like the grid, serial devices, accessing printer
fonts, etc...

We still can't use the Epson Printer Font from .NET 2.0, which means that
receipt printing is either painfully slow or we have to write yet another
dll just for accessing those fonts, which beats the purpose of using .NET in
the first place.

Right now I have to say using .NET in a heavy interop environment was way
more hassle than it was worth, even though the original app was an MFC one.
Plus on the side, customers are already complaining about bad Winforms
performance.

Unfortunately I wasn't in a position to call the shots, otherwise we'd use
native Delphi for rich clients all the way and PHP on the webserver.

..NET might be a nice technology from a developer's perspective, but it
really sucks from the users standpoint.

The only reason for me to use .NET at all is to be able to write games for
the XBox...





.



Relevant Pages

  • Re: Is there any hope for Microsoft ?
    ... VCL 1.0 dead ... VCL: Active development ... WinForms: No further development ...
    (borland.public.delphi.non-technical)
  • Re: Is there any hope for Microsoft ?
    ... VCL 1.0 dead ... VCL: Active development ... WinForms: No further development ...
    (borland.public.delphi.non-technical)
  • Re: My rant about the "throw out delphi and re-write it in C#" crowd.
    ... nothing out there that I've seen for WinForms that hasn't already been ... done to death by 3rd party vendors for VCL? ... thought we were talking about being able to port Delphi applications to ... Drop it on a Windows Form. ...
    (borland.public.delphi.non-technical)
  • Re: 64-bit Windows for AMD 64 is here...
    ... > All that was demonstrated is that VCL.net is less capable than VCL ... than the rather poor WinForms. ... old Win32 API structures in an OO coating. ... I mentioned that one of the strong points of Delphi is is compatibility ...
    (borland.public.delphi.non-technical)
  • Re: My rant about the "throw out delphi and re-write it in C#" crowd.
    ... Visual Studio can still load and use those assemblies with no problems. ... using BDS or Visual Studio will depend on which one does it better. ... will probably surpass VCL in Win Forms V3, ... Anders is not 'behind' WinForms per se. ...
    (borland.public.delphi.non-technical)