Re: DotNet WinForm Development Uptake


"SP" <ecneserpegats@xxxxxxxxxxx> wrote in message
news:%23Aa30hLXGHA.4768@xxxxxxxxxxxxxxxxxxxxxxx
Hi SP,

I suppose its mainly a development decision question. For instance, is
the majority of Windows Desktop development still using traditional tools
and the Win32 API, or is a significant amount (does anybody know of any
estimates?) now carried out using .net?

An estimate of the % of machines that have the framework installed would
be interesting, as one would assume that this would also help to indicate
how much development is going in in .net. e.g. if only 20% of machines
have the framework installed, then it would seem like the uptake is still
quite low.

If you develop using the .Net framework then you are going to come across
machines that do not have the framework already installed (with the
version you require). So the framework becomes the part of your
installation requirements. If this is not acceptable then you should stick
with Win32 development. I came from a VB background so installing runtime
files was something I always had to deal with. The .Net framework made
deployment easier.

HTH

SP

Thanks SP,

I guess the crux of my question is, how successful has Microsoft's .net been
at being accepted by the community that develops Windows Desktop
Applications? I remember reading a long time ago that .net is the way of the
future and the core of Windows will revolve around the technology. - this
was when 1.0 was being released.

But as I search through the newsgroups etc, I see that there appears to be a
lot of developers still against the the .net technology, and it is even
cited that Microsoft has gotten cold feet over .net, with there being less
..net technology built into Vista than originally planned.

On one side you have the anti .net people ranting, and on the other there is
the Microsoft marketing machine telling us all how good .net is. Rather than
read the opinions of the respective sides, I'd like to see what the actual
state of play is so far in terms of a rough % of the win32/.net development
split, and how many machines are estimated to have the framework(s)
installed.

So far trying to get an idea of this information appears to be difficult to
come accross.

James.


.

Relevant Pages

  • Re: VS 2005 - Problems deploying C# executable to target
    ... registry from the last version of the OS before adding the framework ... version of .NET compact framework" doesn't seemtohelp. ... deploying the application, but no combination seems to work. ... sysgen the entire system after this installation? ...
    (microsoft.public.windowsce.embedded)
  • Re: VS 2005 - Problems deploying C# executable to target
    ... The registry is persistent from one ... Framework? ... and tried also with "deploythe latest ... sysgen the entire system after this installation? ...
    (microsoft.public.windowsce.embedded)
  • Re: .NET Framework auf einem USB-Stick ?
    ... > Anwendung auf einem USB-Stick laufen zu lassen, ohne das eine Installation ... Platform Evangelism Division at Microsoft Corp ... Salamander .NET Linker and mini-deployment tool allows you to link .NET ... without installation of the whole Microsoft .NET Framework. ...
    (microsoft.public.de.german.entwickler.dotnet.framework)
  • RE: unable to install ANY .net frameworks to xp professional sp2
    ... Installation failed for component Microsoft .NET Framework 2.0. ... MSI ... returned error code 1603 ...
    (microsoft.public.dotnet.framework)
  • =?iso-8859-1?Q?Re:_Framework_f=FCr_Setup_notwendig=3F?=
    ... Was in aller Welt kann Microsoft für miserable Virenscanner? ... Framework zu tun, ist aber auch so eine kleine Black-Box der man ... Framework +Installation +Problem ergibt 17.200.000 Treffer ... Framework +Installation +Problem ergibt 24.900 Treffer ...
    (microsoft.public.de.german.entwickler.dotnet.framework)