Conversation
Extended the supported target frameworks in Philips.CodeAnalysis.Common.csproj by adding net10.0 alongside net8.0 and netstandard2.0. This change enables the project to build and run on .NET 10.0 in addition to the previously supported frameworks.
Extended the supported target frameworks in Philips.CodeAnalysis.DuplicateCodeAnalyzer.csproj by adding net10.0 alongside net8.0 and netstandard2.0, enabling compatibility with .NET 10.0.
Updated Philips.CodeAnalysis.SecurityAnalyzers.csproj to include net10.0 in the TargetFrameworks property, alongside net8.0 and netstandard2.0, expanding compatibility for the security analyzers package.
Added net10.0 to TargetFrameworks, expanding support alongside net8.0 and netstandard2.0. Other project properties remain unchanged.
Updated Philips.CodeAnalysis.MoqAnalyzers.csproj to include net10.0 in the TargetFrameworks property, alongside net8.0 and netstandard2.0, enabling the project to target .NET 10.0 in addition to existing frameworks.
Extended the supported target frameworks in Philips.CodeAnalysis.MsTestAnalyzers.csproj by adding net10.0 alongside net8.0 and netstandard2.0, enabling compatibility with .NET 10.0.
Changed the TargetFramework in Philips.CodeAnalysis.AnalyzerPerformance.csproj from net8.0 to net10.0 to support the latest .NET version. No other project settings were modified.
Changed the TargetFramework property in Philips.CodeAnalysis.Benchmark.csproj from net8.0 to net10.0 to upgrade the project's framework version. No other modifications were made.
Changed the target framework in Philips.CodeAnalysis.Test.csproj from net8.0 to net10.0 to support newer .NET features and compatibility. No other project settings were modified.
Aravind.H.U (aravind666)
changed the title
Brian Collamore (bcollamore)
left a comment
Brian Collamore (bcollamore)
left a comment
There was a problem hiding this comment.
delete the upgrade md file.
"chore" is correct? This doesn't affect backwards compatibility, right? (I have an action item to upgrade the CodeAnalysis libraries, but that will break compatibility with old stuff, so i was going to increment the major number.)
For the yml's, any reason to keep the 8.0.0 stuff?
I just learnt something new, all analyzers are to be targetted only .netstandard 2.0 we should not target to something like .NET 8 or 10 according to Microsoft, it causes multiple issues when targetted, and also codeanalysis nugget probably we cannot upgrade it has tons of breaking changes. Will update here and postback. |
2 participants
Project target framework modifications