Set dogfood script working directory

[MiYanni]

Summary

With the addition of sdk.paths to the global.json, the dogfood script (used for testing the built SDK in the repo) if ran from the eng folder (the location of the script) won't use the correct SDK. What happens is it'll walk up from eng and find the global.json. Then it will default to the SDK in the .dotnet folder, which is downloaded during the build of the SDK itself, instead of the -dev version:

So, what I did to avoid this problem is made the dogfood script change from the current working directory to the UserProfile (Windows) and Home (Linux/Mac). This means that if you run the dogfood script in the folder it is located, you'll no longer resolve to the global.json of the repo, and thus no longer use the SDK in the .dotnet folder:

[github-actions]

This PR is targeting main, which is now for .NET 11-facing work. If you intended to target .NET 10, either retarget this PR to release/10.0.1xx or make sure you backport the change to release/10.0.1xx after merging. See #50394 for more details.

[Copilot]

Pull Request Overview

This PR fixes an issue where the dogfood script (used for testing the built SDK) would incorrectly resolve to the repo's global.json and use the wrong SDK version when run from the eng folder. The fix changes the working directory to the user's home directory to avoid SDK resolution conflicts.

Key changes:

• Modifies dogfood scripts to change working directory to user home
• Prevents incorrect SDK resolution when scripts are run from their location in the eng folder

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
eng/dogfood.sh	Adds cd command to change to home directory
eng/dogfood.ps1	Modifies prompt function to set location to USERPROFILE

[dsplaisted]

If we want to do this, can we change the directory to artifacts\tmp\Debug instead? That's where most of the tests are run from and usually when I use the dogfood script it's to investigate / debug a project created by tests.

It seems like we would need an empty global.json in that folder to stop the tests from using the wrong SDK version. It doesn't seem like there is one so I'm not really sure how everything is working now.

[MiYanni]

@dsplaisted I haven't tested it, but would using artifacts\tmp\Debug even work? I thought the point of this change was that so there isn't a global.json in the "file tree" from your working directory. Meaning, going up from current dir to the drive root, there's no global.json. I picked the UserProfile dir as it is the default for both cmd and PowerShell. Plus, it's path tree is tiny and highly unlikely to contain a global.json.

[dsplaisted]

@dsplaisted I haven't tested it, but would using artifacts\tmp\Debug even work? I thought the point of this change was that so there isn't a global.json in the "file tree" from your working directory. Meaning, going up from current dir to the drive root, there's no global.json. I picked the UserProfile dir as it is the default for both cmd and PowerShell. Plus, it's path tree is tiny and highly unlikely to contain a global.json.

Yeah I'm confused because I thought we had to put an empty global.json in that folder or the tests wouldn't use the right version of the SDK.

[MiYanni]

@dsplaisted

Yeah I'm confused because I thought we had to put an empty global.json in that folder or the tests wouldn't use the right version of the SDK.

So, looking... the build puts a global.json in a slightly different path: artifacts\tmp\Debug\testing

But that global.json isn't empty either:

It directly points to the built SDK, which makes sense. Do you think this folder makes more sense than the UserProfile?

[nagilson]

Great observation, I think that folder makes more sense than the user profile. It will allow us to configure the experience more and reduce risk of breaking changes from devs having some json file in HOME. Note that this folder does disable CPM.

[MiYanni]

@nagilson @dsplaisted I've updated the path to artifacts\tmp\Debug\testing. PTAL

[MiYanni]

This change requires this change: #51020