No, we are talking about the same thing

- the Dragon installer was confused, and attempted the install of .NET, not recognising that it was already installed (an unfortunately common problem which can lead to further problems down the line) the installer itself should have recognised the situation, and may either have backed out gracefully, or run a 'repair install' of .NET and this should have left the updates in place.
Sometimes the installation is forced, and this can lead to a touch of DLL Hell - with the result that the .NET installation cannot be updated, and causes problems in removal as well, and has to be hoicked out by a dedicated removal tool and reinstalled from scratch. Luckily such forced installs are relatively rare.
Keep an eye out for any failed .NET updates over the next few patch Tuesdays, but I think you're probably good to go