Skip to content

Conversation

@agocke
Copy link
Member

@agocke agocke commented Jun 30, 2021

The version is currently hardcoded in TestCaseUtils.cs, but since
these are reference assemblies, as long as the surface area isn't
predicted to change, we can update as necessary.

The version is currently hardcoded in TestCaseUtils.cs, but since
these are reference assemblies, as long as the surface area isn't
predicted to change, we can update as necessary.
@agocke agocke requested a review from marek-safar as a code owner June 30, 2021 00:19
@agocke agocke requested a review from tlakollo June 30, 2021 00:19
public static readonly ReferenceAssemblies Net6PreviewAssemblies =
new ReferenceAssemblies (
"net6.0",
new PackageIdentity ("Microsoft.NETCore.App.Ref", "6.0.0-preview.5.21224.4"),
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not very familiar with ReferenceAssemblies creation but I assume the package identity version doesn't need to be maintained unless we actually need newer ReferenceAssemblies, we just took one version and rely on it even if the linker global.json changes, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup, that's the idea. Unless there's a breaking change in the reference assemblies, we shouldn't care which exact version we use.

@agocke agocke merged commit f549b4e into dotnet:main Jun 30, 2021
@agocke agocke deleted the net6-ref branch June 30, 2021 02:01
agocke added a commit to dotnet/runtime that referenced this pull request Nov 16, 2022
The version is currently hardcoded in TestCaseUtils.cs, but since
these are reference assemblies, as long as the surface area isn't
predicted to change, we can update as necessary.

Commit migrated from dotnet/linker@f549b4e
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