Skip to content

Conversation

@jaredpar
Copy link
Member

@jaredpar jaredpar commented Aug 17, 2024

This moves us to use Basic.Reference.Assemblies for our net40 test
assets. This saves ~200MB of I/O on CI restore.

This is a purely mechanical change. The bulk of the changes is

  • Rename Net40.mscorlib to Net40.Resources.mscorlib
  • Add an Import or using for Basic.Reference.Assemblies

Functionally there should be no change here.

Note there is one test change in RefStructInterfacesTests (see second commit). Adding Basic.Reference.Assembiles.Net40 also updated to the newer version of Basic.Reference.Assemblies.Net90. That effectively moved us from Preview3 to Preview6 and that has the updated version of Activator.CreateInstance. Needed to update a baseline to account for that.

@ghost ghost added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Aug 17, 2024
This moves us to use Basic.Reference.Assemblies for our `net40` test
assets. This saves ~200MB of I/O on CI restore.

This is a purely mechanical change. The bulk of the changes is

- Rename `Net40.mscorlib` to `Net40.Resources.mscorlib`
- Add an `Import` or `using` for `Basic.Reference.Assemblies`

Functionally there should be no change here.
@jaredpar jaredpar marked this pull request as ready for review August 17, 2024 16:23
@jaredpar jaredpar requested review from a team as code owners August 17, 2024 16:23
@jaredpar
Copy link
Member Author

@dotnet/roslyn-compiler PTAL

$buildTool = InitializeBuildTool
$frameworkArg = if ($framework -ne "") { " -p:TargetFramework=$framework" } else { "" }
$buildArgs = "$($buildTool.Command) -v:m -m -p:RunAnalyzersDuringBuild=false -p:GenerateFullPaths=true$frameworkArg $($projectFileInfo.FullName)"
$buildArgs = "$($buildTool.Command) -v:m -tl:off -m -p:RunAnalyzersDuringBuild=false -p:GenerateFullPaths=true$frameworkArg $($projectFileInfo.FullName)"
Copy link
Member Author

Choose a reason for hiding this comment

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

The terminal logger isn't compatible with the VS Code problem matcher.

Copy link
Member

Choose a reason for hiding this comment

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

If we preferred the terminal logger, we could write a matcher for it. https://code.visualstudio.com/Docs/editor/tasks#_defining-a-problem-matcher

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

Labels

Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead VSCode

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants