Re: There is no .NET in Vista Code?

Chris Burrows wrote:

One of the great things for developers producing .NET applications is that this trend has at last been reversed.

Maybe you are thinking of Delphi .NET apps? These certainly have some significant overhead but that is a Delphi problem not a .NET problem.

Typically my non-VCL, non-Delphi .NET apps are less than 1/10th of the size of the original Delphi Win32 app that I translated.

Obviously in that size discussion you would be excluding
for the sake of your argument the size of the framework
run-time, the size of the assemblies of the components that
most significant apps have to ship, etc.

Jeez, you could make that self same (false) argument about
the size reduction benefits for Delphi exes through checking
"build with run-time packages"... :-P

The requirement for the user to download the .NET framework is the only thing that is holding me back from distributing .NET apps. However, it is a very short-term issue. Sooner rather than later it will be pre-installed along with the OS (some manufacturers are already doing so). It will be no more necessary to download and install the framework than it was to download and install Comctl32.dll and all the other Win32 dlls needed for your Win32 app to run.

I was hoping myself that at some point the framework would
be "baked in" to OS releases such that the re-distribution
issue would be killed...but I see no evidence that this will
be the case. Version 2.0 of the framework will be pre-installed
for Vista but when version 3.0 of the framework rears its head
(or even some unforeseen v2.1 release) the installed base for
that latest version of .NET slips back to zero...

Far from being a "very short-term issue", re-distribution of
the framework looks more to me like a "for the foreseeable
future" issue...
.

Relevant Pages

  • Re: Lets think who will like to say delphi is dying?
    ... All important Software ist still native and will be native in the future, there is a market for delphi, they only need to pick it up. ... I have tried every thing I could get my hands on for windows and none come as close to Delphi in terms of productivity and ease of use. ... I like .NET but the UI is just too slow and .NET apps use too much memory. ... At corporate level everywhere only those tools are utilized which have got a large following of developers and thus it is easy to find developers for that tools. ...
    (borland.public.delphi.non-technical)
  • Re: There is no .NET in Vista Code?
    ... Maybe you are thinking of Delphi .NET apps? ... Pascal for .NET version exe is a sleek sexy 44K. ... The requirement for the user to download the .NET framework is the only ...
    (borland.public.delphi.non-technical)
  • Re: PC Plus magazine (UK) - Delphi 8 review
    ... Alan Garny wrote: ... > wagon at this stage. ... to go into full production of .net apps, most want the tool in order to ... > used Delphi before. ...
    (borland.public.delphi.non-technical)
  • Re: VB coverage in new online mag - VB6 or VB.NET?
    ... >> in .Net apps later as we see the need to deliver .Net apps. ... Delphi is rich in ... > it really compete with VB? ... not consider VB a real development tool, they don't respect the language, ...
    (microsoft.public.vb.general.discussion)
  • Re: .NET - end user reality check
    ... one app that even refuses to install. ... We needed the new CRM system on the machine so uninstalled the other framework version and Prophet subsequently installed fine. ... One common feature of .Net apps seems to me to be the lack of decent ... error messages that appear when something does go wrong. ...
    (borland.public.delphi.non-technical)