My stackoverflow question was closed so here's a blog post about CoreWCF

2025-05-08 My stackoverflow question was closed, so here's a blog post about CoreWCF I'm preparing a blog post on remote procedure calls (RPC) and Interprocess Communication between .NET Framework and dotnet 8, but while doing so I ran into an issue with a service getting stuck consuming CPU after a client has closed. It's not a good fit for asking Claude, etc., because there's too much confusion on whether you're talking about CoreWCF, WCF client on .Net Core ( System.ServiceModel nuget package version ), or WCF on .NET Framework ( System.ServiceModel from the framework ). This is confusing enough for humans, let alone a machine that will happily reproduce calls and configuration from something that is almost identical, yet subtly different and incompatible. I didn't want to raise a github issue, because I doubt I've found a bug in WCF, especially since it feels like what I'm trying to do is probably a misunderstanding of how WCF streams are supposed to work. I'm also quickly hitti ... Read full article.