Well, six patches later, done one at a time, they all seemed to go in successfully.
They sure took a lot of time to do their thing during installation.
But all checks are green, all patches show up in Add / Remove and no sirens went off.
So, I am now committed to .NET, it seems, and expect traffic every Patch Tuesday until I move on to W7.
Maybe I should get busy on that update!
Thanks again for the help and hand-holding here.
Last edited by DrRon; 2012-04-26 at 11:08.
Glad that it all went well. I believe that's what happens in most cases .
DrRon: Not to burst your bubble, but W7 does not get you out of patch tuesday, and it does not get you out of frequent .net updates, either. I'm running W7 on 3 pc's and have programs needing .net on them all. It still seems like a constant stream of updates to .net.
Good points all. I am running Win7 Home Premium and have just installed all .net patches as they have come along and have never had a problem of any kind. And I do have a rigorous backup procedure automated and a system image just in case, but I've never had a problem, nor has anyone I know. My company is still running XP Pro and we install patches two weeks after release across our network, after they've been vetted, and all of the .net patches have worked just fine there too. I think the problem must be smaller than we've been led to believe. :^)
Originally Posted by ruirib
There is at least one web site, the Grant County Map Server that requires Silverlight to access it. I found out one day when I tried to access that same site while running Ubuntu. I have found that the web site error message will inform you that you need Silverlight to access it. I can't believe the taxpayers got stuck with a proprietary system, but hey, it's government. What else can you expect?