Re: .NET - end user reality check

Kostya wrote:

> Win32 and Windows in general had taken years and years to become
> what it is now. It'll probably take quite a while
> to bring .NET to the same state.

And in the meantime Win64 is here, and it looks unforgiving..

Win64 vs. .NET

Who will rule?
.

Relevant Pages

  • Re: As programmers...have we come a long way since 1993?
    ... If 'win64', as the main OS of PC users, ... is notably different in compatibility with old win32 software then ... the case Win64 should be largely tolerant of win32, ... > Look at Windows XP and Windows 2000, with that very scary DCOM exploit. ...
    (comp.programming)
  • Re: The Future of native code
    ... the API targeted for 64-bit versions of Windows" ... But I still wonder about the future of native Delphi in the Win32 world. ... So, even risking being wrong as it can be dangerous to do "futurology" in IT, I'd say that CodeGear has enough Win32 and Win64 around for a few more decades. ... And if that runtime somehow fails to install, how well do you think those users will be able to "fix" it? ...
    (borland.public.delphi.non-technical)
  • Re: .Net and 64-bit
    ... Peter Morris wrote: ... Win32 or Win64. ... The version of Windows that the OP has doesn't tell you if it's a 32 bit system, but it tells you if it's a 64 bit system. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Vista and .NET (Win32 life may be limted)
    ... but it will happen for the 32-bit API ... Maybe when there's a 128-bit version of Windows. ... Plus Win64 is pretty much Win32 with bigger integers. ...
    (borland.public.delphi.non-technical)
  • Re: Exported function for x64 bit
    ... example that your custom SDK have 10+ DLLs exporting some symbols used by ... You are supporting Win32 as well as Win64. ... Win64 callers will call your Win64 DLL ...
    (microsoft.public.vc.language)