<sa*@discardmail.comwrote:
Only if the required OS is installed, of course...
Yes, but programs created for windows will run standalone on all
windows platforms.
No. If I write something which uses Vista-specific calls, it won't run
on XP.
C# not.
Unless you've got Vista or Win2K, of course...
But many people have WinXP right now and will continue for a long
time.
True - so they won't be able to use Vista-specific programs either.
But interesting view. Never thought about this argument. But... For C?
Could be that some lib needs patching... I also think my apps are more
hurt able then the framework. :)
Not sure what you mean here.
I mean that the standard user will be not aware that the .net
framework needs updating. If he doesn`t use windows update he won`t
get a fixed version.
True - but I would hope that most people who care about security even
*slightly* use Windows update these days.
All programmms can have security problems. Therefore them need
updates.
Yes - so they should have Windows update on. Note that an update to a
"just the managed code" program is likely to be a lot smaller than an
update to a "managed code and framework combined" program - not to
mention the fact that if you have 3 programs which all need updating
due to the same framework bug, you'd have to update all 3 (having been
contacted by the suppliers) rather than having Windows Update just fix
it.
A lot of people have Windows Update turned on - but how many regularly
check for newer versions of *every* application they run?
If you write in C you will probably use external sources aswell too.
Those can include security holes. As a developer you must relay on
news so or so and update your apps then.
Indeed, unless those are covered by Windows update.
That C# compiled sources (.exe) need that .net framework to run is one
of the biggest disadvantage of C# imho. Guess for that reason no
"professional developers" like devs for games/antivirus and so on
don`t use .net right now.
At least one anti-virus company uses .NET for some of their management
tools, IIRC. Games have tended to need "close to the metal" access
which .NET hasn't provided very well before, although XNA may make a
difference. The unpredictability of the GC (in terms of pauses) is a
problem for games, too.
Both my current job and my previous job have involved writing "shrink-
wrapped" .NET applications though.
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog:
http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too