Add .NET Core solution open to OptProf training scenarios

[ladipro]

Fixes #6067

Context

There is a few dozen milliseconds worth of avoidable JITting happening in MSBuild assemblies on VS solution open. The respective methods are considered cold and not part of our NGEN images because they are not executed by current training scenarios.

Changes Made

Added an additional scenario to specifically cover .NET Core projects.

Testing

Ran the OptProf pipeline with this change and then Perf.DDRITs with a build optimized using the resulting optimization data.

• 50 ms less CPU spent JITting Microsoft.Build!*
• Perf.DDRITs showing improvements:
  • WebToolsVS64.SolutionManagement 0100.Open Solution - devenv methods JITted down by 24.4%
  • WebToolsVS64.SolutionManagement 0200.Rebuild Solution - non-devenv methods JITted down by 4.5%
  • ManagedLangsVS64.RebuildSolution 0100.Rebuild Solution - non-devenv methods JITted down by 12.1%
  • CPlusPlusVS64.SolutionManagement 0300.Change Solution Configuration - Cold - devenv methods JITted down by 2.1%
  • A few RefSet counters improved by a bit as well.
• Impact on native image size is +490 kB (+4 %).

[rainersigwald]

I see it's called OpenClose test. Do we have a scenario covering a basic build of this project type?

[Forgind]

Sounds like a nice win. Is there somewhere I can look at the solution?

[ladipro]

I see it's called OpenClose test. Do we have a scenario covering a basic build of this project type?

Surprisingly, no. I wasn't able to find one that we could just reference. I think it would make perfect sense to add it as well (under src\Tests\MSBuild in the VS repo, for example). Another potential change I'm tracking is making our assemblies use full (as opposed to partial) NGEN, so even code that's not covered in training scenarios is pre-compiled.

Sounds like a nice win. Is there somewhere I can look at the solution?

Absolutely, the test uses this asset: internal link.