[release/6.0] Fix Microsoft.VisualBasic.Core file version #62908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #62218
Customer Impact
When doing some refactoring on how we calculate assembly versions we accidentally removed a property that calculated the file version embedded into the assembly. When an application is compiled as self-contained and bundled into an MSI file, upgrading from a previous (e.g. .NET 5) which can lead to this assembly missing on the installation location or the wrong assembly to be used.
Testing
VIsual inspection of the assembly to make sure the file version is correct and higher than the ones in previous releases.
Risk
Low, this is just changing the file version embedded into the assembly.