Skip to content

Conversation

am11
Copy link
Member

@am11 am11 commented Sep 27, 2021

Runtime has switched to net7.0. This PR adds support for 7.0 in BDN.

IMO, we should look into removing hard coded mechanism (enums, --tfm / --cli options etc.). There are just too many redundant moving parts and it is not scaling well.

/// CoreRT compiled as net6.0
/// </summary>
public static readonly CoreRtRuntime CoreRt60 = new CoreRtRuntime(RuntimeMoniker.CoreRt50, "net6.0", "CoreRT 6.0");
public static readonly CoreRtRuntime CoreRt60 = new CoreRtRuntime(RuntimeMoniker.CoreRt60, "net6.0", "CoreRT 6.0");
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seemed like a bug so I fixed it.

@AndreyAkinshin AndreyAkinshin self-requested a review September 28, 2021 10:18
@AndreyAkinshin AndreyAkinshin added this to the v0.13.2 milestone Sep 28, 2021
@AndreyAkinshin AndreyAkinshin merged commit a5176a7 into dotnet:master Sep 28, 2021
@AndreyAkinshin
Copy link
Member

@am11 thanks for the PR!

IMO, we should look into removing hard coded mechanism (enums, --tfm / --cli options etc.)

Well, it's not an easy problem. I agree that we have a decent number of different TFMs. However, this set is still maintainable. Meanwhile, hard coded values in API help to easily discover available options. Also they provide a strictly typed way to work with TFMs.

@adamsitnik what do you think on this?

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