From: "Geo." 

"Mike N."  wrote in message
news:1tp9q29204f3lqmddsslb3qeo9mhn5de1a{at}4ax.com...

>>versions. And then when they do patch all 4 versions and 24% of their apps
>>break they can't tell which broke.
>
>  The end user just runs Windows Update.   The Uber geek runs Shavlik.
> Security patches always risk breaking apps.  Is there any other solution?

Ok so patch tuesday comes, you do your update, and tomorrow you find an app
that doesn't work anymore. Was it a .NET patch or one of the other patches,
next monday you find a second app that's not working, same question except
this time was it .NET 1.0 patch or .NET 2.0 patch or both or neither?

>   The difference from Java is that the version granularity is much
> coarser.   There is V1.0, V1.1 and V2.0.  None of this java junk of 2.00.1
> leaving an unpatched 2.00.0 in place on your system; the libraries are
> patched in place.

I'm not sure I understand, what's the difference between having two
applications, one which requires java 1.x and the other java 2.x and having
two applications one that requires .NET 1.0 and one that requires 2.0?

Geo.

--- BBBS/NT v4.01 Flag-5