-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Don't overwrite pinned assembly versions in servicing #84079
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
02eb3a8
bdc7cf6
3a09813
958f4ff
09dd019
7356d63
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are eight packable projects that pin their assembly version for .NET Framework compatibility. The incremental package servicing infrastructure didn't check if the assembly version is pinned and always changed it. As an example, System.Speech pins its assembly version to 4.0.0.0 but that version gets overwritten during servicing. I.e. for .NET 7 the version would then change to "7.0.0.$(ServicingVersion)" which is incorrect. Please find the full list of impacted assemblies below: - System.ComponentModel.Composition - System.DirectoryServices - System.DirectoryServices.AccountManagement - System.DirectoryServices.Protocols - System.Management - System.Reflection.Context - System.Runtime.Caching - System.Speech
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,8 +1,6 @@ | ||
| <Project> | ||
| <Import Project="..\Directory.Build.props" /> | ||
| <PropertyGroup> | ||
| <!-- AssemblyVersion is frozen to that which originally shipped in 2.1 --> | ||
| <AssemblyVersion>4.0.0.0</AssemblyVersion> | ||
|
Comment on lines
-4
to
-5
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This library only ships inside the Microsoft.NETCore.App shared framework. I assume we don't need to pin its assembly version anymore?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it once had a package and this is left over from that time.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What is the expected side-effect of removing AssemblyVersion from here?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The assembly will version in the same way as every other assembly that ships only in the targeting packs (N.0.0.0 which remains frozen in servicing). |
||
| <StrongNameKeyId>ECMA</StrongNameKeyId> | ||
| </PropertyGroup> | ||
| </Project> | ||
Uh oh!
There was an error while loading. Please reload this page.