Eric StJohn

Still something wonky happening with the build of the analyzer that I haven't quite determined. Looks to me like it's building concurrently in two separate processes. Here's the nuspec diff...

/azp run MachineLearning-CI

/azp run MachineLearning-CI

I'm going to rename the projects to CSProj and put everything in the sln to make this work better with fewer custom steps.

@michaelgsharp/@viktorhofer can you take another look at this? I'm going to stop short of pipeline refactoring on this and do that in a separate PR.

Here's an updated diff of NuSpecs, comparing the latest from main with the updates in this PR: https://github.com/ericstj/diffs/commit/26178c06087ac37c140a6bcac94ea6b3b1efb8ab

@AraHaan can you link to what installers you're trying to install? I just gave this a try using our public installers and they both block installation: https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-6.0.1-macos-arm64-installer ``` Dec 14...

This is implemented here: https://github.com/dotnet/installer/blob/8b9782a074c51ef9f8b8b0608870c23ed77df7f5/src/redist/targets/packaging/osx/clisdk/Distribution-Template#L5 And here, for runtime: https://github.com/dotnet/runtime/blob/eb4834060d7c6d3bbdb2eae8a3312c8a6a726146/src/installer/pkg/sfx/bundle/shared-framework-distribution-template-arm64.xml#L4 Perhaps you're trying to install an intermediate pkg artifact which we don't consider a shipping installer?

I added some script usage of installation-check downlevel that has user-visible strings in script. We're unlikely to change that downlevel even if we fix loc for 6.0 or 7.0, however...

> whichever version you installed last is the one you're going to get. That's not the way most installer technology works. Most components / products have a version that is...