Skip to content

Burn and .NET Framework 4.8 #6713

You must be logged in to vote

Very likely this issue: A little while back, Microsoft decided to release all the .NET Framework binaries with new signatures at the same URLs. This broke everyone validating the .NET Framework thumbprint, including existing Burn bundles. It was pretty disruptive. We had to help a couple of FireGiant customers navigate emergency updates.

Could it happen again? Yes. Microsoft could choose to make a breaking change and post it to the same URL. Will they? They didn't do it for many years, never was clear why they did it this time.

Replies: 1 comment 1 reply

You must be logged in to vote
1 reply
@TrulsHaraldsson

Answer selected by TrulsHaraldsson
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants