The compat change is we’re trading a compile-time success and runtime failure (native compiler) against a compile-time error (restoring the behavior of v1.2).
The scenario is loading an assembly where some methods, fields or nested types have accessibility flags set to 7 (all three bits set), which mean public AND private.Īfter the fix, such flags are loaded to mean private. PR: dotnet/roslyn#5144 Version 1.3.0 Treat a method marked with both public and private flags as private Previously the user would get a NullReferenceException for synchronous methods and an AggregateException containing a NullReferenceException for asynchronous methods. PR: dotnet/roslyn#4169 Changed Simplifier methods to throw ArgumentNullExceptionsĬhanged Simplifier.ReduceAsync, Simplifier.ExpandAsync, and Simplifier.Expand methods to throw ArgumentNullExceptions if any non-optional, nullable arguments are passed in. There seems to be little risk that we broke any customers here and hence we decided to remove this API.
Creation of the parsers is meant to be done via the Default singleton properties. It was never the intent for these members to be a part of the supported API surface. This in turn made many of the protected members of CommandLineParser a part of the API surface as it gave external customers an inheritance path. API Breaking Changes Version 1.1.0 Removed VisualBasicCommandLineParser.ctorĭuring a toolset update we noticed the constructor on VisualBasicCommandLineParser was public. Sourced from 's releases.NET 7.0 Preview 5 Updates from 3.11.0 to 4.5.0 Release notes Bumps MicrosoftCodeAnalysisVersion from 3.11.0 to 4.5.0.
0 kommentar(er)
