-
Notifications
You must be signed in to change notification settings - Fork 15
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
Check compatibility with .NET 8 #196
Comments
I faced strange error. |
Thank you for the example. I'll include it in some of my tests. The current dscom version is not yet built with .NET 8. It's likely that most interactions with System libraries from .NET 8 will create errors. |
The dscom problem is rooted in the fact that for some reason |
The behavior in connection with the System.Security.Cryptography library is moved into a separate issue #210 , because it's not a general problem with .NET 8 |
* feat: Added .NET 8 Build Targets #196 * chore: Removed some warning introduced by .NET 8 #196 * chore: moved suppressions to the editorconfig * chore: removed warning that is handled by the editorconfig * chore: Added missing documentation and remove warnings * fix: global.json uses the same config as BuildProps * fix: Turned back the global.json to use .NET 8 * chore: Removed compile warnings --------- Co-authored-by: Mark Lechtermann <[email protected]>
We need to check how .NET 8 compatibility can be achieved and how .NET 8 will affect our tool.
https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-8
The text was updated successfully, but these errors were encountered: