Skip to content

Update Apigen to support .NET 6#1300

Merged
lukebakken merged 3 commits into6.xfrom
update-apigen
Feb 21, 2023
Merged

Update Apigen to support .NET 6#1300
lukebakken merged 3 commits into6.xfrom
update-apigen

Conversation

@Zerpet
Copy link
Copy Markdown
Member

@Zerpet Zerpet commented Feb 17, 2023

Proposed Changes

Without specifically setting net6.0 as a target framework,
it is impossible to run Apigen project on M1 Macs, because
support for M1 Macs was added in .NET 6, according to this
post in MS forums [1].

Apparently, supporting .netstandard2.0 is not enough, at least locally,
to build and run the Apigen project.

This change is needed to enable developers on M1/M2 Macs to
develop code using branch 6.x as base.

[1] https://learn.microsoft.com/en-us/answers/questions/793925/problem-installing-with-dotnet-on-m1-macos-archite

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Further Comments

Marked this change as 'cosmetic' since .NET 6 was already supported via .netstandard2.0,
and this PR is basically adding support for .NET installations on ARM64 chips.

Edit: marked milestone as 6.5.0, but I see no reason why this can't go into 6.4.1, since it's just an internal change for developers.

Without specifically setting net6.0 as a target framework,
it is impossible to run Apigen project on M1 Macs, because
support for M1 Macs was added in .NET 6, according to this
post in MS forums [1].

To enable support for .NET 6, we had to add a NuGet dependency.
Everything else worked out of the box.

[1] https://learn.microsoft.com/en-us/answers/questions/793925/problem-installing-with-dotnet-on-m1-macos-archite

Signed-off-by: Aitor Perez Cedres <acedres@vmware.com>
@Zerpet Zerpet added this to the 6.5.0 milestone Feb 17, 2023
@Zerpet Zerpet force-pushed the update-apigen branch 2 times, most recently from 2e50039 to 77e2da7 Compare February 17, 2023 18:11
Signed-off-by: Aitor Perez Cedres <acedres@vmware.com>
@Zerpet
Copy link
Copy Markdown
Member Author

Zerpet commented Feb 17, 2023

Looks like I broke the Concourse build as well. I'll look into that 👀

@Zerpet
Copy link
Copy Markdown
Member Author

Zerpet commented Feb 20, 2023

Fixed CI for this PR 🔨

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants