-
Notifications
You must be signed in to change notification settings - Fork 641
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
Package was restored using .NETFramwork=v4.6.1 #1318
Comments
I'm also getting this. I would like to know if this is something to be concerned about. |
the package fo-dicom.imaging.desktop requires System.Drawing. Is there any issue with System.drawing and .net 6? Will GDI be deprecated in .net 6 and replaced by some other packages? |
I am not sure about what is happening with GDI but VS2022 runs so much faster so it is worth the upgrade if you have a lot of ram. |
Maybe the warning has to do with the fact that |
Oh, i thought System.Drawing was always only supported under Windows. That's why it is only included in the nugetpackage fo-dicom.Imaging.Desktop, while on all other platform it is recommended to use fo-dicom.Imaging.ImageSharp, or no package at all and use the byte-arrays of pixels directly (RawImage). |
If you are using fo-dicom.imaging.desktop, then you are bound to Windows anyway, and therefore somehow referencing .netframework will not limit your application further. |
I was actually wrong, it's System.Drawing.Common what I was referring to, not |
I had the same problem so I pulled down the repo, created a .Net-project file (Net 6.0), added the source-files, added System.Drawing.Common 6.0 as a Nuget-packet and it seems to work without any dependencies to .Net Framework. |
I am getting the following when I added fo-dicom.Imaging.Desktop 5.0.2 to a .NET 6 WPF app. The app seems to work fine.
The text was updated successfully, but these errors were encountered: