[release/9.0] Update Windows.Compatibility external packages. #4900
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update Windows.Compatibility external packages ServiceModel is updated to 8.1.1, in this version System.ServiceModel.Security and System.ServiceModel.Duplex no longer exist, their types (type forwards) are in the primitives package. Microsoft.Data.SqlClient NuGet package to 4.9.0 --------- Co-authored-by: Tanya Solyanik <[email protected]>
Tanya-Solyanik
changed the title
|
Waiting to pick up version from dotnet/runtime#112139 |
Tanya-Solyanik
changed the title
Tanya-Solyanik
changed the title
|
We should raise the risk level on this - it's updating the major version of a dependency - something we typically do not do in servicing.
@Tanya-Solyanik you don't need to wait on anything. That version should flow automatically, just like other runtime packages. |
Tanya-Solyanik
commented
Mar 6, 2025
WCF team prepared a new version of client
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #4884
Description:
Microsoft.Windows.Compatibility NuGet v8.0.12 carries 3 assemblies(System.Data.SqlClient.dll, System.Diagnostics.EventLog.Messages.dll, and System.ServiceModel.dll)) that do not have symbols on the Microsoft symbol server.
Fix:
System.Data.SqlClient.dll and System.ServiceModel.dll – updated to a newer compatibility packages that have symbols
System.Diagnostics.EventLog.Messages.dll – pdbs were added to the package in the above mentioned PR, and will flow to Microsoft.Windows.Compatibility as a servicing update
Followup bugs
Symbol package questions · Issue dotnet/runtime#15457 · dotnet/arcade
What is the expected workflow for Symbols Validation of official releases? · Issue dotnet/arcade#15537 · dotnet/runtime
Customer Impact:
Partner can’t debug their tests. They can’t upgrade. Windows partner has to store pdbs locally to be accessible for the duration of windows support term, which is longer that the .NET8’s. To achieve this goal they are down loading pdbs from the symbol server, their script breaks on our package.
Testing:
built the windows compatibility pack and verified that the right package versions are referenced.
Verified that the new partner packages have pdbs
Risk:
High - updating the major version of a dependency