Delete orphans and fix build suggestions

[gewarren]

Fixes #33658

[gewarren]

The snippets 5000 error is strange. Is it an error on my side, or did something change recently with Snippets 5000? @adegeo @IEvangelist

[BillWagner]

This LGTM @gewarren

I'm also really confused by the exceptions in the Snippets 5000. We haven't updated the package in our repo in a while. That stack trace isn't part of the .NET executable. @adegeo Is it coming from a package in the powershell script?

[IEvangelist]

Hi @BillWagner and @gewarren - the errors are simply being reported by the PowerShell script, see these lines:

Write-Host "Total errors: $count"

foreach ($er in $errors) {

# ...

In the Get-MSBuildResults.ps1 there are three places where System.IO.Path.Combine are called, and these automation stack traces look reminiscent of that of PowerShell.

It's claiming that path1 is null, which is possible here https://github.com/dotnet/docs/blob/main/.github/workflows/dependencies/Get-MSBuildResults.ps1#L150.

Total errors: 32
Error: ERROR: System.Management.Automation.MethodInvocationException: Exception calling "Combine" with "2" argument(s): "Value cannot be null. (Parameter 'path1')"
 ---> System.ArgumentNullException: Value cannot be null. (Parameter 'path1')
   at System.IO.Path.Combine(String path1, String path2)

I think this could be prevented with a guard there, but we'll have to verify with @adegeo.

[gewarren]

The Snippets 5000 errors are expected. Quoted from how-to-run-a-workflow.md:

    > [!NOTE]
    > Please replace `Workflow1` in these examples with `FlowchartNumberGuessWorkflow`, `SequentialNumberGuessWorkflow`, or `StateMachineNumberGuessWorkflow`, depending on which workflow you completed in the previous [How to: Create a Workflow](how-to-create-a-workflow.md) step. If you do not replace `Workflow1` then you will get build errors when you try and build or run the workflow.