Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Sep 21, 2022

The Microsoft public key token was only applied to the source assembly but not to the contract. Fixing this by moving the StrongNameKey property into the parent Directory.Build.props file, same as we do for other libraries.

I think we should backport this change into release/7.0 to avoid potential customer observable issues.

The Microsoft public key token was only applied to the source assembly but not to the contract.
@ViktorHofer ViktorHofer self-assigned this Sep 21, 2022
@ghost ghost added the area-Serialization label Sep 21, 2022
@ViktorHofer ViktorHofer changed the title Fix public key token for Serialization.Schema lib Fix public key token for Serialization.Schema contract Sep 21, 2022
@ViktorHofer ViktorHofer changed the title Fix public key token for Serialization.Schema contract Fix public key token of Serialization.Schema contract assembly Sep 21, 2022
Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. How did you catch this?

@ViktorHofer
Copy link
Member Author

ViktorHofer commented Sep 21, 2022

With the new roslyn-based APICompat tooling that we are migrating to via #73263 (comment). The tooling flagged the in-compatibility between the contract and the implementation.

@ViktorHofer ViktorHofer merged commit f595e02 into main Sep 21, 2022
@ViktorHofer ViktorHofer deleted the ViktorHofer-patch-3 branch September 21, 2022 14:58
@ViktorHofer
Copy link
Member Author

/backport to release/7.0

@github-actions
Copy link
Contributor

Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/3098867926

@ghost ghost locked as resolved and limited conversation to collaborators Oct 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants