Introduction

One common issue developers face when transitioning from .NET Framework to .NET Core (or its successor, .NET 5 onwards) is the "System.ServiceModel not found" error. This issue arises primarily due to differences in how .NET Core handles WCF (Windows Communication Foundation) services compared to the traditional .NET Framework environment. This article delves into the technical aspects of why this issue occurs and how developers can address it in their .NET Core projects.

Understanding System.ServiceModel

In the .NET Framework, System.ServiceModel is a namespace that provides a range of classes necessary for building service-oriented applications, particularly those leveraging WCF. WCF enables seamless communication across various systems and platforms by allowing developers to build secure, reliable, and transacted messaging systems.

However, when the transition was made to .NET Core, not all features of the .NET Framework were ported over due to compatibility and architecture reasons. As a result, developers may encounter an error indicating that System.ServiceModel is not found when attempting to use WCF-related services in their .NET Core projects.

Why System.ServiceModel is Missing in .NET Core

.NET Core was designed to provide a more modular, cross-platform framework that differs fundamentally from the .NET Framework. Consequently, only a subset of the original .NET Framework libraries was included in .NET Core, based on cross-platform capabilities and developer needs.

Some of the reasons WCF is only partially available in .NET Core include:

1. Platform Agnosticism: .NET Core is designed to be platform-independent. However, parts of WCF are inherently Windows-centric, particularly those depending on Windows activation and authentication mechanisms.
2. Modernization: As RESTful services and other modern protocols have gained popularity, the need for a fuller WCF service in cross-platform environments has diminished, leading to partial support in .NET Core.
3. Focus Shift: Microsoft has shifted its focus towards newer technologies such as gRPC, which provides better cross-platform capabilities and performance in distributed systems.

Solutions for System.ServiceModel in .NET Core

While System.ServiceModel is not fully implemented in .NET Core, there are solutions developers can explore to work around this limitation:

1. Use `CoreWCF`: A community-driven open-source project that aims to provide WCF server capabilities in .NET Core. CoreWCF offers a similar programming model that should feel familiar to developers with existing WCF experience.
2. Examine Alternative Protocols: Consider using gRPC for new service development. gRPC is supported fully in .NET Core and offers advantages such as better performance with HTTP/2 and strong API contracts with Protocol Buffers.
3. Use .NET Core Compatible Libraries: Some aspects of WCF client capabilities have been ported to .NET Core. Developers can utilize packages like `System.ServiceModel.Http`, `System.ServiceModel.NetTcp`, and others to enable certain WCF client-side functionalities.
4. Hybrid Approach: For existing systems that heavily rely on WCF, consider creating a hybrid environment where WCF services run on .NET Framework, and you integrate them with .NET Core applications through HTTP or other supported protocols.

Example Scenario

Suppose your existing application uses WCF services to handle business-to-business transactions. Upon migrating to .NET Core, you realize that the critical `NetTcpBinding` specified in System.ServiceModel is missing. Here's how you can address this: