WCF on Framework vs Core alternatives
Your enterprise still has WCF SOAP services on .NET Framework. What are realistic options on .NET Core / .NET 8?
Answers use simple, clear English.
Quick interview answer
Full WCF server stack is Framework-centric. Options: (1) keep WCF on Framework and strangler new features, (2) CoreWCF for selected SOAP contracts, (3) replace with gRPC/REST + OpenAPI for internal/public APIs, (4) WCF client packages exist on Core for calling legacy services. Prefer contract adapters during coexistence.
Detailed answer
Full WCF server stack is Framework-centric. Options: (1) keep WCF on Framework and strangler new features, (2) CoreWCF for selected SOAP contracts, (3) replace with gRPC/REST + OpenAPI for internal/public APIs, (4) WCF client packages exist on Core for calling legacy services. Prefer contract adapters during coexistence.
Real example & use case
Partner SOAP stays via CoreWCF; internal mesh moves to gRPC.
Pros & cons
Pros: phased modernization. Cons: dual protocols and ops overhead.