Upgrade projects to .NET 10 (System.Web) by gewarren · Pull Request #12810 · dotnet/dotnet-api-docs

gewarren · 2026-06-25T21:22:04Z

Contributes to #12513.

This reverts commit 27c0003.

Copilot

Pull request overview

This PR contributes to issue #12513 by retargeting the System.Web.Services.* C# snippet projects from .NET Framework (net472) to .NET 10 (net10.0), aligning snippet compilation with modern .NET.

Changes:

Updated many snippets/csharp/System.Web.Services.Description/**/Project.csproj projects from net472 to net10.0.
Updated snippets/csharp/System.Web.Services.Configuration/**/Project.csproj projects from net472 to net10.0.
Normalized one project from <TargetFrameworks> to <TargetFramework> while upgrading.

Reviewed changes

Copilot reviewed 82 out of 82 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
snippets/csharp/System.Web.Services.Description/SoapHeaderBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapHeaderBinding/Message/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapHeaderBinding/MapToProperty/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapFaultBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapBodyBinding/PartsString/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapBodyBinding/Encoding/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapBinding/Style/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapBinding/Namespace/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/SoapAddressBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionImporter/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionFormatExtensionCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetService/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetPortType/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetMessage/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetBinding/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionBaseCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Types/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Namespace/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Messages/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Imports/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Extensions/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/CanRead/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Bindings/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceCollection/Insert/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceCollection/Contains/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/ServiceCollection/Add/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Service/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Service/Extensions/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/CopyTo/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/Contains/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/Add/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortType/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortType/Operations/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortCollection/CopyTo/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/PortCollection/Add/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Port/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationOutput/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationMessageCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationMessage/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationInput/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationFlow/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationFaultCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationFaultCollection/Item/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationFaultCollection/Add/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationFault/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationBindingCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/OperationBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Operation/ParameterOrder/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Operation/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Operation/IsBoundBy/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Operation/Faults/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimeXmlBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimeTextMatchCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimeTextMatch/Capture/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimeTextBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimePartCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimePartCollection/Add/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimePart/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimeMultipartRelatedBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MimeContentBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MessagePart/Message/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MessageCollection/Contains/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/MessageBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Message/FindPartByName/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/InputBinding/Overview/Project.csproj	Retarget snippet project to net10.0 (and normalize TargetFramework property).
snippets/csharp/System.Web.Services.Description/ImportCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/HttpBinding/Namespace/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/HttpAddressBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/FaultBindingCollection/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/FaultBindingCollection/Item/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/FaultBindingCollection/Contains/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/FaultBinding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/DocumentableItem/Documentation/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/BindingCollection/Add/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Binding/Overview/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Description/Binding/Extensions/Project.csproj	Retarget snippet project to net10.0.
snippets/csharp/System.Web.Services.Configuration/XmlFormatExtensionAttribute/Overview/Project.csproj	Retarget snippet project to net10.0.

Comments suppressed due to low confidence (82)

snippets/csharp/System.Web.Services.Description/SoapHeaderBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapHeaderBinding/Message/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapHeaderBinding/MapToProperty/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapFaultBinding/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapBodyBinding/PartsString/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapBodyBinding/Encoding/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapBinding/Style/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapBinding/Namespace/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/SoapAddressBinding/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionImporter/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionFormatExtensionCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetService/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetPortType/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetMessage/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionCollection/GetBinding/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescriptionBaseCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Types/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Namespace/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Messages/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Imports/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Extensions/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/CanRead/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceDescription/Bindings/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceCollection/Insert/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceCollection/Contains/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/ServiceCollection/Add/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/Service/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/Service/Extensions/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/CopyTo/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/Contains/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortTypeCollection/Add/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortType/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortType/Operations/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortCollection/CopyTo/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/PortCollection/Add/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/Port/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationOutput/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationMessageCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationMessage/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationInput/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationFlow/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationFaultCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationFaultCollection/Item/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationFaultCollection/Add/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationFault/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationBindingCollection/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/OperationBinding/Overview/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.
snippets/csharp/System.Web.Services.Description/Operation/ParameterOrder/Project.csproj:9
These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/Operation/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/Operation/IsBoundBy/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/Operation/Faults/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimeXmlBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimeTextMatchCollection/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimeTextMatch/Capture/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimeTextBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimePartCollection/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimePartCollection/Add/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimePart/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimeMultipartRelatedBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MimeContentBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MessagePart/Message/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MessageCollection/Contains/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/MessageBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/Message/FindPartByName/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/InputBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/ImportCollection/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/HttpBinding/Namespace/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/HttpAddressBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/FaultBindingCollection/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/FaultBindingCollection/Item/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/FaultBindingCollection/Contains/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/FaultBinding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/DocumentableItem/Documentation/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/BindingCollection/Add/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/Binding/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Description/Binding/Extensions/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

snippets/csharp/System.Web.Services.Configuration/XmlFormatExtensionAttribute/Overview/Project.csproj:9

These snippets now target net10.0, but the project still references System.Web.Services, which is the .NET Framework assembly name. For modern .NET (net6+ / net10), these APIs are surfaced from the System.Web.Services.Description assembly/package, so this reference is likely to break snippet compilation. Update the reference to System.Web.Services.Description (or switch to an explicit PackageReference) to match the target framework.

    <TargetFramework>net10.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Reference Include="System.Web.Services" />

Removed example section illustrating CodeGenerationOptions enumeration usage.

Copilot

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

…-docs into upgrade-csharp-set20

gewarren added 3 commits June 25, 2026 14:13

Upgrade projects to .NET 10

27c0003

Upgrade projects to .NET 10

23d7696

Revert "Upgrade projects to .NET 10"

4e4e59b

This reverts commit 27c0003.

dotnet-policy-service Bot assigned gewarren Jun 25, 2026

gewarren requested a review from Copilot June 25, 2026 21:37

Copilot started reviewing on behalf of gewarren June 25, 2026 21:38 View session

Copilot AI reviewed Jun 25, 2026

View reviewed changes

gewarren added 3 commits June 25, 2026 15:36

delete netfx snippets

fb53996

resolve merge conflict

e14fd5b

delete netfx snippets

43ac923

gewarren requested a review from Copilot June 26, 2026 00:05

Copilot started reviewing on behalf of gewarren June 26, 2026 00:05 View session

Remove example from CodeGenerationOptions documentation

852d8fc

Removed example section illustrating CodeGenerationOptions enumeration usage.

Copilot AI reviewed Jun 26, 2026

gewarren added 2 commits June 25, 2026 17:30

remove orphaned example intros

2447cad

Merge branch 'upgrade-csharp-set20' of github.com:gewarren/dotnet-api…

5c3263a

…-docs into upgrade-csharp-set20

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Upgrade projects to .NET 10 (System.Web)#12810

Upgrade projects to .NET 10 (System.Web)#12810
gewarren wants to merge 9 commits into
dotnet:mainfrom
gewarren:upgrade-csharp-set20

gewarren commented Jun 25, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

gewarren commented Jun 25, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants