fix(codegen): added .net6 as target framework due to issues with directive #300
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Agreed... But somehow this was working fine on x64 based systems but not ARM64. Might be a bug in .NET/MSBuild since the behaviour changes according to the CPU architecture. Thanks for merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed
TargetFrameworkto include multi-target similar to other Chr.Avro projects (such asChr.Avro.Binary,Chr.Avro.Confluent,Chr.Avro.JsonandChr.Avro).The reason behind this change is because the
NET6_0_OR_GREATERdirective is not working on .NET Standard projects (at least on ARM64 architecture). This workaround will however work on .NET 6+ since the framework package is used instead of the netstandard one.