You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mallikac/remove-bcl-memory-from-wilsonAzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet:mallikac/remove-bcl-memory-from-wilsonCopy head branch name to clipboard
mallikac/remove-bcl-memory-from-wilsonAzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet:mallikac/remove-bcl-memory-from-wilsonCopy head branch name to clipboard
You've included unit or integration tests for your change, where applicable.
You've included inline docs for your change, where applicable.
If any gains or losses in performance are possible, you've included benchmarks for your changes. More info
There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
The proposal includes three steps as below. This PR covers the first step listed below.
Proposal:
Covered in this PR
Microsoft.Bcl.Memory is only for pre-net9 TFM; the new APIs are available in .NET 9. Remove this dependency and restore older implementation for netstandard2.0 and lower TFMs.
One more comment: I'm splitting the work into two PRs as below:
Covered in this PR
Microsoft.Bcl.Memory is only for pre-net9 TFM; the new APIs are available in .NET 9. Remove this dependency and restore older implementation for netstandard2.0 and lower TFMs.
Covered in next PR
Remove System.Text.Json reference for net9.0 TFM Update Microsoft.Extensions.Logging.Abstractions to 8.0.0 for .NET9.0 from 8.0.2
I was thinking this makes sense because:
To separate out changes
reduce size of PR for ease of review
Is that alright to do or should I keep it all in one?
One more comment: I'm splitting the work into two PRs as below: Covered in this PR
Microsoft.Bcl.Memory is only for pre-net9 TFM; the new APIs are available in .NET 9. Remove this dependency and restore older implementation for netstandard2.0 and lower TFMs. Covered in next PR
Remove System.Text.Json reference for net9.0 TFM Update Microsoft.Extensions.Logging.Abstractions to 8.0.0 for .NET9.0 from 8.0.2
I was thinking this makes sense because:
To separate out changes
reduce size of PR for ease of review
Is that alright to do or should I keep it all in one?
nit: Consider moving the preprocessor directives inside the method if all targets share the same API signature. To keep the file clean, you could introduce a static class (e.g., LegacyBaseUrlEncoder) for pre-.NET 9 implementations, either in this PR or a follow-up cleanup.
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
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.
Remove Microsoft.Bcl.Memory 9.0 in Wilson
Summary of the changes (Less than 80 chars)
Description
This PR removes the reference to Microsoft.Bcl.Memory in Wilson, and replaces it with the older version referenced here: Use new Base64Url API (#2817) · AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet@c0eb23c.
The proposal includes three steps as below. This PR covers the first step listed below.
Proposal:
Covered in this PR
Fixes #3224 (in this specific format)
For Testing: