Microsoft IE11 update foxes Telerik dialogue boxes Microsoft’s March Windows 10 Update has claimed a new victim: Windows dialogue boxes built using Telerik objects. Telerik has received “numerous reports” of Microsoft’s IE update breaking RadWindow and RadListBox, according to an email to users seen by The Reg. This followed the release by Microsoft of its March update last …
How many times will it have to happen before MS figures out the fact that one mega-patch doesn't work as well as releasing the individual patches for individual issues?
If $PartX interferes with $PartY then you can hold back on either of those two parts, release the rest, & fix everything else. If you roll them up into a single mega-patch then *everything* gets delayed while you try to work out the conflict between those two individual parts. Or did the Febuary FuckUp not do a good enough job of pounding that lesson home?
Stop the mega-patch SNAFU, go back to individual patches, & let some sanity have a chance of soaking through your thick skulls.
"How many times will it have to happen before MS figures out the fact that one mega-patch doesn't work as well as releasing the individual patches for individual issues?"
It doesn't make that much difference. You should be testing the patch, and if it breaks something, you don't apply the "mega-patch" until it's fixed. If you have a real reason to need a separate hotfix for something in the patch, Microsoft PSS can usually assist...
"It doesn't make that much difference. You should be testing the patch, and if it breaks something, you don't apply the "mega-patch" until it's fixed. If you have a real reason to need a separate hotfix for something in the patch, Microsoft PSS can usually assist..."
How is the run of the mill home computer user suppose to do that? Web mail is a stretch for many of them.
"It doesn't make that much difference. You should be testing the patch..."
You've completely missed the point. Of course we test patches, but if one doesn't work I still very much want the rest installed to resolve the other issues rather than remain completely vulnerable.
I also don't expect to waste my time calling vendor support in order to do so; my time is much more valuable than that.
>Stop the mega-patch SNAFU, go back to individual patches
Then they would have to tell you what each patch does. It goes completely against cloud philosophy.
And it assumes that they could back out the patch if it goes wrong. Well, Apple doesn't do that so obviously there's no good reason for MS to do anything different.
It's no joke.
IE upgrades have broken Telerik controls in the past.
And it's not specific to Telerik, or IE. Every 3rd-party dependency you add to your project is another risk. Will it work in the next version of Windows/.NET/IE/Visual Studio? If the publisher's still around, and if they're still supporting the product, and if you're still paying them for updates, then hopefully yes, but that's a lot of ifs.
In the Microsoft ecosystem, it really is safest to stick to what Microsoft hands down. And if you scrub yourself with bleach when you get home, you can still go to sleep feeling only slightly dirty.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
