Document -u option for updating service references in dotnet-svcutil

[Copilot]

Plan to add instructions for updating references

• Understand the issue and explore repository
• Add a new section documenting the -u option for updating references
• Ensure the new section follows Microsoft documentation style guidelines
• Validate the changes by reviewing the output
• Remove tab versions and show only the latest way per feedback

Changes made

Added a new section "Updating the service reference" that:

• Explains how to update existing service references using the -u option
• Provides the command syntax for the latest version (dotnet-svcutil): dotnet-svcutil -u .\path\to\reference\folder
• Documents that the reference folder should contain the ConnectedService.json file
• Explains how the tool uses this configuration file to regenerate the proxy code

Updated per review feedback to show only the latest version without tabs.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Please add instructions for updating references</issue_title>
<issue_description>The tool help summarizes this, but it took me a bit to figure it out. I think it should be:

dotnet svcutil -u .\path\to\reference\folder

Where the referencefolder contains the saved ConnectedService.json file.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3d0bd854-fec8-fc4a-760a-42dc22e07f99
• Version Independent ID: f04e9f8b-24d2-79fb-7521-6222c434e80f
• Content: WCF svcutil tool overview - .NET Core
• Content Source: docs/core/additional-tools/dotnet-svcutil-guide.md
• Product: dotnet-core
• GitHub Login: @mlacouture
• Microsoft Alias: mairaw</issue_description>

Comments on the Issue (you are @copilot in this section)

@mairaw Thanks for your feedback @shoop. @mlacouture what do you think of adding this? Can you handle that? @dotnet-bot This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.</comment_new>

• Fixes Please add instructions for updating references #14395

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Internal previews

📄 File	🔗 Preview link
docs/core/additional-tools/dotnet-svcutil-guide.md	WCF dotnet-svcutil tool for .NET Core

[meaghanlewis]

@copilot please remove the tab versions and just have one version of the latest way of completing a task.

[Copilot]

@copilot please remove the tab versions and just have one version of the latest way of completing a task.

Removed the tab versions. The section now shows only the latest command: dotnet-svcutil -u .\path\to\reference\folder (commit a16ec11)

[Copilot]

Pull request overview

This PR adds documentation for the -u (update) option in the dotnet-svcutil tool, addressing a user request for clearer instructions on updating existing service references. The changes also simplify the documentation by removing version-specific tabs and focusing on the latest tooling.

Changes:

• Added new "Updating the service reference" section that documents the -u option for updating existing service references
• Simplified documentation by removing tab-based version selection (1.x vs 2.x) throughout the document
• Updated heading from "Using the Service Reference" to "Using the service reference" to follow sentence case convention

[gewarren]

Should we remove the references to .NET Core and just use ".NET" instead?