News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Patch Lady – .NET changes

    Posted on April 20th, 2019 at 18:00 Susan Bradley Comment on the AskWoody Lounge

    Back in the 7 and 8.1 era .NET was independently released and not part of the operating system – exactly – yes each shipped with a base .NET version, but other versions would come out and be offered up to those platforms.  On some platforms (you know we are talking about you Small Business Server) it became common knowledge that you did not upgrade .NET on that platform and just serviced it as is.

    Then along came Windows 10 with it’s cumulative patching model with everything patched in one shot.  If you wanted to upgrade to a newer .NET you didn’t install it, it came with the feature release.  And .NET updates on Windows 10 were not separate, they came with the cumulative update.  Well…. until 1809.  When 1809 was released the .NET updates separated back out from the operating system and you could separately install them.

    Coming with Windows 10 1903 .NET 4.8 will be released.  So far consistent, yes?  Well not so fast.  Once again Microsoft is changing .NET patching so that .NET is uncoupled again from the operating system.  .NET 4.7 was supported on Windows 10 anniversary edition  (I think that’s 1607? Can’t keep track of them)

    As noted in the .NET blog post

    Updates for .NET Framework 4.8 on Windows 10 versions 1607, 1703, 1709, 1803 and Server 2016 will now be delivered independently and side by side with Windows cumulative updates.

    Before to upgrade to a new .NET you had to go up a feature update to do so.  Now you can install .NET 4.8 on Windows 10 all the way back to 1607.  And when you do so, those .NET updates will be offered up separately from the Windows 10 operating system updates.

    I honestly think this is a good thing.  Lord knows my line of business apps don’t move to support new platforms as fast as they should.  But it is hard for me to try to keep track of what does what where on what platform and who’s on first and what’s on second and … you get the idea.  I honestly do not want to go back to the Windows 7 patch model of separate patches as I think the cumulative model – once we get the patch quality to where it should be – is what we need to do as it keeps our machines more secure – but at the same time you can tell that as Microsoft is listening to our complaints about patching, they are moving back to a model where things are more modular and optional.

    So Microsoft?  Good on you for listening and making changes in patching.  Now get that quality up.

    If that helped, take a second to support AskWoody on Patreon