liveBook · Manning

WCF

As explained in ASP.NET Core in Action, 3e

WCF is Microsoft's .NET framework for building service-oriented applications that communicate through configurable messaging endpoints.

WCF (Windows Communication Foundation) is Microsoft's .NET framework for building service-oriented applications that communicate through configurable messaging endpoints. In ASP.NET Core, support is partial rather than a complete replacement for .NET Framework WCF. section 2.4.3

When assessing a move to ASP.NET Core:

  • Build client-side WCF services with the libraries provided by ASP.NET Core. section 2.4.3
  • Build server-side WCF services with the Microsoft-supported, community-driven CoreWCF project. section 2.4.3
  • Check required APIs first: distributed transactions and some message security formats are unsupported. section 2.4.3
  • Treat applications built with WCF as harder ASP.NET Core conversions, especially when their existing service APIs are essential. section 2.4.3

How ASP.NET Core in Action, 3e covers it

How deep it goes
Defines partial client and server support, but stops short of comprehensive WCF API coverage or implementation guidance.
Examples
Uses client-side libraries, CoreWCF server hosting, distributed transactions, and message security formats as concrete compatibility examples.
What you can do after
Evaluate whether ASP.NET Core can replace a WCF application by checking hosting needs and unsupported APIs.
How it connects
Connects WCF with ASP.NET Core, .NET Framework, CoreWCF, Web Forms, and web API migration.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.