[GitHub] [avro] KalleOlaviNiemitalo commented on pull request #1956: AVRO-3670: Add NET 7.0 support

[GitBox <gi...@apache.org>]

KalleOlaviNiemitalo commented on PR #1956:
URL: https://github.com/apache/avro/pull/1956#issuecomment-1339534120

   If the implementation does not use any new features of .NET 7, then it might be better to **not** target net7.0 in the Apache.Avro.Tools package, and instead allow major version roll-forward so that the binary built for net6.0 can be run on computers that have only .NET 7 installed. This would avoid increasing the size of the tool package and would also allow running on .NET 8 and later.
   
   <https://learn.microsoft.com/dotnet/core/project-sdk/msbuild-props#rollforward> describes the `RollForward` property with which a C# project can configure this. AFAICT, the Avro repository does not set this property yet.
   
   <https://github.com/dotnet/sdk/issues/26417#issuecomment-1172672371> suggests making .NET SDK warn if a tool is packaged without allowing major version roll-forward.
   
   Building with a .NET 7 SDK can still be beneficial if it enables new analyzers.
   
   Re upgrading the System.CodeDom package from 6.0.0 to 7.0.0, what are the end-of-support dates of these package versions? <https://dotnet.microsoft.com/en-us/download/dotnet> shows that .NET 6.0 support will end on November 12, 2024; but .NET 7.0 support will end earlier, on May 14, 2024. Does System.CodeDom share the support timeline of .NET, or is only the latest version of the package supported?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@avro.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org