How many PCs in the world have the .NET Framework installed?
I did a second .NET Framework features informal poll recently, and as with all .NET related polls the question comes up: How many PCs have the .NET Framework on it?
If you're a company that is considering creating a client application using .NET (not Silverlight, but the .NET Framework) you'd probably like to know if your end-user needs to install something extra to use your app.
So I started asking questions. We've said things here and there about the pervasiveness of the .NET Framework but I wanted to get the final word (at the time of this writing) and put it somewhere easy to fine.
After some digging, here's what I've got:
- Well over 90% of the PCs in the world have some version of the .NET Framework installed.
- Over 65% of Windows PCs in the world have .NET 3.5 SP1 installed.
This is a lot higher than I thought, and it's pretty cool.
The .NET Framework is smaller than you'd think (that's why I wrote SmallestDotNet). The very small .NET 4 Client Profile makes it easier (both speed and download size) to put .NET on a machine.
I think these numbers will help folks who might be considering using .NET for a client application.
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
Just to make sure it's clear, this isn't the results from a poll. These is not limited to my readers, these are statistics from telemetry (Windows Update, etc) reporting as given to me by the bosses.
Thanks.
Btw, is there a place where these statistics are updated and publicly visible (like the browsers statistics at w3schools)?
(a) not running windows
(b) not online
(c) not using windows update
Is automatically excluded. I bet, if you ran an analysis, less than 5% would appear to be running OSX
</cynism>
With Windows 7 obviously things can only get better for us although then we will want to be deploying with .NET 4 :-)
p.s. What happens if you use the .NET Client Profile and a program happens to call for instance System.Web?? I assume this would not be in the client profile although I have a valid reason involving code reuse to have it included in one of my projects. Is it a friendly error or an unexplained .NET crash?
That doesn't give any indication of the *actual* worldwide market share of .NET (unless Unix, Linux, Mac OS X, etc, start using windows update, of course... )
You are probably missing the point. If these numbers are being shown in an attempt to say "Hey, don't worry about designing a Client App in .NET" they do the job just fine.
The reason being is you have to think of distribution of said Application. If you are distributing it over the internet:
- The percentage of users on PCs who don't use a Windows OS for their desktop is incredibly small...even the most staunch Linux supporter will conceed this point (your point A, plus they could run Mono making it moot anyways).
- You don't care about people who aren't online (point B).
- If someone is online and not using Windows Update, chances are they're using a pirated copy of the OS, which makes them an unlikely candidate to purchase your Winforms/WPF app anyways (point C).
On the other hand, if you distribute via CD or DvD, you can just include the.NET runtime installer.
What I'd like to see is US/Canadian numbers, are those available?
Andrew
Fundamentally we are interrogating internet traffic around the globe (LOTS OF IT) so it is not biased or skewed to "high IQ users" but is a reasonable view of the broad internet connected PC population.
Hope this helps provide some color.
Thanks,
Brian Goldfarb
Director, Developer Platforms and UX
Microsoft Corporation
In that case, I'd say 65% is a pretty amazing (and encouraging) stat!
Scott, that just gave me an idea: it would be cool to see a riastats.com-like site for .NET installs. I know you can get that info from the useragent so it ought to be reasonably easy to collect and analyze. The hard part would be getting participation from some major sites.
I wonder how many developers are targeting .Net 2 vs .Net 3.5 sp1... From my (limited) perspective I think the solid nature of .Net 2 as a stable base for everything has led a lot of companies to not allowing their developers to move past that point. Companies view .Net 2 as a solid safe bet, but still view .Net 3.5 as an addon. The fact that .Net 3.5 and .Net 3.5 SP1 have HUGE amounts of differences in terms of features adds a lot of confusion around the adoption I think.
.NET 4 Client Profile will be in Windows Update as well. Rabi Satter said this on his blog (he works for Microsoft in the Deployment Team):
.NET 4 will be released on Windows Update (WU). In addition, it will show up in Windows Server Update Service (WSUS). Specifically .NET Framework 4 Client Profile will be released as a recommended update on Vista and Windows 7. A recommended update will be automatically installed depending on the Automatic Update settings. Client Profile will also be released as an optional update for XP. With XP a user will have to manually run WU and select the .NET Framework 4 Client Profile. Windows 2003, Windows 2008 and Windows 2008 R2 will see .NET Framework 4 as an optional update.
So that means that .NET 4 *will* for most machines connected to WU, be automatically installed.
http://www.globaltechmatrix.com/
Brian convincingly suggests that the numbers are not skewed.
I'm personally at a loss how traffic analysis can identify PC's (in order to count individual ones, i.e.).
In that vein I'm at a loss how to intepret some of these figures. E.g. adding the browser market shares for IE _and_ Firefox (you see, I'm being liberal there, just to accommodate) you'd get at 62.69 + 24.61 = 87.3%. Citing 90%+ .NET adoption is than quite a surprise IMHO
But then again... NetApps statistics on OS trends do not match my view of things, so its probably my view that needs adjusting. Personally, I'd keep very critical of this kind of statistic as (a) it is not clear how NetApps can even identify PC's* (b) it is not what I see in my personal or work environments. Granted, I'll revoke my <cynism/> until I have my own counts (like: never).
Cheers,
* At best it comes down to 'best effort' where, just like in school, the loudmouths win (the PC's that generate the most traffic to be analysed, i.e.)
Regards,
Preeti Sharma
Business Development Officer
Ampere Software Private Limited
Contact: +1-800-315-0433
E-mail: preetis@amperesoftware.com
URL: www.amperesoftware.com
So just requiring IE6 or above on the client is still the safe (but rather painful) option.
Does the 65% installed base for .net 3.5 apply to the .net 3.5 SP1 client profile or the full .net 3.5 SP1 redist or any version of .net 3.5 SP1?
Thanks
Matt
Comments are closed.