On Thu, 22 May 2008 19:36:12 +0200, "Michel Posseth [MCP]"
On anny Windows computer connected to the internet it is pretty safe to
asume that the .Net framework is installed
You might even built a Installer that checks for the correct framework
and
if it is not installed download and install this from the MS website
It is easy for developers and IT pros to presume and
require that everything is updated, but unless you are
running a setup program that installs the framework
automatically if needed (with all that is required is for
the user to click next next next ...), it is *not* safe to
assume that Mr. and Mrs. Jones have updated their
home computer.
First of all, there are people who consistently answer "No" to
any plea from the Windows Security Center or to the
Windows Update notification in the SysTray (I know some of
them). Second of all, last time I checked, the .Net
Framework was an optional update (this might have
changed), which means that even if a machine is configured
to install updates automatically, the framework is not included
as it is not a critical update. I think the framework service
packs are critical, but I do not remember.
Then there are the situations where the (optional?) framework
update is selected, but fails to install (due to bloatware
preinstalled on notebooks nowadays?)
In a corporate environment with a sysadmin watching
the machine park like a hawk, no problem, but never
make any assumptions about the state of a home user's
machine or the same user's ability to do anything about
it. If Internet Explorer works, that is all that matters. And
who cares if the 60-day trial version of Norton Antivirus
that came preinstalled has not been updated for two years?
The machine is still running, so why change anything?
Ok, let me make a small correction: Even in the corporate
environment do we find sysadmins who refuse to install
the framework, thinking it is going to mess with the OS.
Then there are the server admins who do not allow version
2.0 to be installed on their servers because they need to run
software that depends on version 1.1 and still harbour doubts
that the two frameworks can coexist peacefully on the same
machine.
Then there are the old machines with low memory. Try installing
XP SP2 on a tablet pc running Windows XP Tablet Edition 2005
(or whatever it is called). Installing SP2 installs Framework 2.0 AND
burdens the OS with a few system tools, so suddenly just starting
the OS takes up an additional 50MB of memory compared to when
it was just running SP1. There goes another (albeit small) group of
machines where people might be hesitant to install the framework
(as part of the SP2 install).
Finally, there are still people on dial-up connections (or worse: who
pay for the amount of traffic) who might be happy to download a 1MB
application to try it out, but not if it means downloading an
additional 50MB framework (or much more for .Net 3.5) before they
can run it.
Did I forget the latest Eee PC or OLPC craze where they are starting
to shoehorn Windows XP into 4GB of flash memory? I do not know if
.Net 2.0 is included on those machines, but I do not think there is
much left over for the owners to be wasteful with it.
I do not know the stats for .Net (consumer) market penetration,
but I do not believe we are quite there yet.
Google:
http://discuss.joelonsoftware.com/default.asp?biz.5.592012.13
Ah! I remember in the good old 90'es when I released a freeware
VB6 program and people were complaining that the installer was
6MB too large due to the VB6 runtime files and that I ought to
switch to a real programming language like Delphi. After a few
years, the complaints went away and people thought nothing
of downloading a 10MB installer. Someday, .Net will get to that
point too.
Another question might be,, do you want your programs to run on
outdated
computers wich do not have the required servicpacks installed
thus users blaming your software while it are actually solved bugs ?
Even a machine that came with Windows XP preinstalled could
be considered outdated (7+ years old?) by today's standard, so
setting XP as the baseline is unlikely to cut out too large an
audience.
Regards,
Joergen Bech