-
Notifications
You must be signed in to change notification settings - Fork 631
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
Upgrade Nuget package to use CommunityToolkit instead of Microsoft toolkit as it is depreciated. #1473
Labels
Comments
@Dash-Ravi - do you want to create a PR for this? |
@mrbean-bremen sorry for the delayed reply. I will try for this and will submit the PR when I am done. |
Thanks for notifying us 👍 |
akojo
added a commit
to akojo/fo-dicom
that referenced
this issue
Feb 9, 2023
Microsoft.Toolkit.HighPerformance is no longer maintained. Switch to using its successor CommunityToolkit.HighPerformance.
akojo
added a commit
to akojo/fo-dicom
that referenced
this issue
Feb 9, 2023
Microsoft.Toolkit.HighPerformance is no longer maintained. Switch to using its successor CommunityToolkit.HighPerformance.
3 tasks
mrbean-bremen
pushed a commit
that referenced
this issue
Feb 9, 2023
Microsoft.Toolkit.HighPerformance is no longer maintained. Switch to using its successor CommunityToolkit.HighPerformance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is, according to you, missing from fo-dicom? Please describe.
Currently, Fo-Dicom is using Microsoft.Toolkit.highperformance nuget package which is depreciated and it's alternate is Communitytoolkit.Highperformance.
Describe the solution you'd like
Change Nuget package to Communitytoolkit.Highperformance from Microsoft.Toolkit.highperformance
Describe possible alternatives or existing workarounds you've considered
A clear and concise description of any alternative solutions or existing workarounds you've considered.
The text was updated successfully, but these errors were encountered: