What problem does it solve? Maintaining Windows Communication Foundation services on .NET Framework involves complex binding, security, and hosting configuration, and teams often struggle to decide whether to keep WCF or migrate endpoints to modern stacks like gRPC, ASP.NET Core, or CoreWCF. ## Core Features & Use Cases - WCF Configuration Guidance: Keep bindings, behaviors, contracts, throttling, and security settings explicit to avoid hidden defaults and production failures. - Migration Decision Framework: Evaluate per-endpoint whether to stay on WCF or move to gRPC, REST/ASP.NET Core, or CoreWCF based on WS-* requirements, client ecosystem, and transport dependencies. - Maintenance Patterns: Apply proven patterns for fault contracts, versioning, hosting (IIS, self-host, Windows Service), diagnostics, reliable sessions, and client proxy lifecycle. - Use Case: A team running a SOAP service with WS-Security requirements needs to containerize on .NET 6+. Use this Skill to inventory endpoints, map contracts to CoreWCF bindings, and plan an incremental endpoint-by-endpoint migration while keeping existing SOAP clients working. ## Quick Start Ask the AI to review your WCF service configuration and recommend whether each endpoint should stay on WCF or migrate to gRPC, REST, or CoreWCF.