Skip to content

doc: fix stale build guidance in doc/building.md#20450

Open
nsfxdyj wants to merge 1 commit into
microsoft:mainfrom
nsfxdyj:dev/docs-building-17880
Open

doc: fix stale build guidance in doc/building.md#20450
nsfxdyj wants to merge 1 commit into
microsoft:mainfrom
nsfxdyj:dev/docs-building-17880

Conversation

@nsfxdyj

@nsfxdyj nsfxdyj commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes #17880. Updates doc/building.md to match how the repository actually builds today:

  • Remove the stale git submodule update --init --recursive instructions. The repository no longer uses git submodules (there is no .gitmodules file), so this step silently does nothing and confuses new contributors.
  • Add a Troubleshooting section covering the two NuGet restore failures reported in the issue:
    • NU1101: Unable to find package Microsoft.*.App.Ref — these reference packages ship with the .NET SDK (8.0 and 10.0, both in .vsconfig), not with the configured feeds.
    • 401 (Unauthorized) from the TerminalDependencies Azure Artifacts feed — the feed allows anonymous read access; a 401 is typically caused by stale cached credentials, with guidance on how to clear them.

Verified against a fresh clone + full local build (x64 Debug, 0 errors).

The repository no longer uses git submodules, so drop the submodule
restore instructions from doc/building.md (there is no .gitmodules).

Also add a Troubleshooting section covering the two NuGet restore
failures reported in microsoft#17880:

- NU1101 for Microsoft.*.App.Ref packages: these ship with the .NET
  SDK (8.0 and 10.0 are required), not with the configured feeds.
- 401 (Unauthorized) from the TerminalDependencies feed: guidance for
  clearing stale cached credentials.

Fixes microsoft#17880
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@DHowett

DHowett commented Jul 20, 2026

Copy link
Copy Markdown
Member

You and #20400 will need to fight it out I guess.

@nsfxdyj

nsfxdyj commented Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

@DHowett Ha, fair! I took a look at #20400 and it's a clear superset of what I have here (the nuget.exe upgrade and the deploy-walkthrough fixes are genuinely valuable, and it covers the same submodule/NuGet points). Happy to let that one land first — I can rebase afterward to fill in any remaining gaps, or close this PR if it ends up fully covered. Whichever you prefer.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Please update building documentation

2 participants