1---2name: dotnet-wcf3description: Work on WCF services, clients, bindings, contracts, and migration decisions for SOAP and multi-transport service-oriented systems on .NET Framework or compatible stacks.4---56# Windows Communication Foundation78## Trigger On910- working on WCF services, bindings, or clients11- deciding whether a service should stay WCF or move to modern HTTP APIs12- reviewing transport, security, or interoperability settings1314## Workflow15161. Use WCF where SOAP, WS-* features, or multi-transport service requirements are real; do not rewrite those needs into HTTP-only guidance by accident.172. Keep contracts, bindings, behaviors, and hosting configuration explicit because WCF complexity compounds through configuration indirection.183. For new REST-style services, prefer modern ASP.NET Core APIs instead of extending WCF into a shape it is no longer best suited for.194. Plan migrations per endpoint and capability: transport, security model, transaction requirements, metadata, and client compatibility.205. Validate interoperability and deployment assumptions with the actual client ecosystem, not only local service startup.216. When WCF coexists with ASP.NET, be explicit about which runtime behaviors are shared and which are not.2223## Deliver2425- stable WCF service or client configuration26- realistic migration guidance to newer stacks where appropriate27- clear contract and binding ownership2829## Validate3031- WCF is used for a reason the modern stack does not replace directly32- binding and security behavior are explicit33- interop is verified with real consumers3435## References3637- [migration.md](references/migration.md) - WCF to gRPC/REST/CoreWCF migration paths, decision framework, and endpoint-by-endpoint migration strategy38- [patterns.md](references/patterns.md) - WCF maintenance patterns for configuration, contracts, hosting, security, diagnostics, and client proxy management