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
Add net6.0
as a target framework
#616
Commits on Apr 8, 2022
-
Add
net6.0
target, and NoWarn for SYSLIB0003Code Access Security (CASE) is only supported on .Net Framework; from net5.0 onwards it is marked obsolete which causes build warnings. For now, easiest to disable the warnings. If/when fully deprecated, it may be necessary to be a bit cleverer.
-
Use
RuntimeInformation
to avoid CA1416 warning for COM interop hand……ling when not on Windows Marshal.GetIUnknownForObject causes a CA1416 warning unless the code is only running on Windows. It is unclear how well Mono handles COM interoperability, so whether special handling is needed for Mono.
-
Add
EventLog
handling fornet6.0
, add nicer handling for Mono in ……tests for `DiagnostlicsLogger` There are `CAS1416` errors if attempting to use `EventLog` on `net6.0` without handling to ensure the platform is Windows, hence the need to use `SupportedOSPlatform` at the class level for the DiagnosticsLogger-related classes.
-
Update build pipelines for
net6.0
support, add GitHub Actiosn pipel……ine to solution for ease of access
-
-
Add
ref/*-net6.0.cs
files, update test/generator to work only under…… `net6.0` Changed the generation from `net472` to `net6.0` due to errors when trying to load a `net6.0` assembly from `net472`
-
-
-
-
Commits on Apr 10, 2022
-
Remove references of DOTNET462 as no longer used
The sole usage of DOTNET462 (PublicApiTestCase) now uses NET6_0. There are symbols such as NET462 and NET462_OR_GREATER (supplied by the SDK) if such switching is required in future.
-
Commits on Apr 30, 2022
-
Switch to preprocessor directives to avoid need for System.Runtime.In…
…teropServices.RuntimeInformation package on net462