3 ms·
Thank you for tuning in here. I imagine that WCF was one of the first parts to be converted. How mature is the Core .NET WCF now?
by vadimberman 9y ago
Thank you for tuning in here.
I imagine that WCF was one of the first parts to be converted. How mature is the Core .NET WCF now?
- barake 9y ago.NET Core does not have an implementation of WCF, and I can’t imagine to ever will. .NET Core has a pretty good MVC framework you can build REST services on, GraphQL, or gRPC etc. Most of the framework baggage was left behind.
- akoeplinger 9y agoThere's https://github.com/dotnet/wcf https://github.com/dotnet/wcf which are the _client_ libraries of WCF for .NET Core. For the server side of WCF you're right those are only available on .NET Framework right now.
- maxxxxx 9y agoI hope they won't port WCF. wCF makes simple things complicated.
- vadimberman 9y agoFor me personally, WCF made complicated things trivial. My startup was able to get into Fortune 100 enterprises with all their insane compliance requirements, letting their IT departments configure things the way they see fit. Once you get the hang of it, WCF is one of the best frameworks EVER written.
- jsingleton 9y agoThis is a bit complex, but for what most people think of as WCF (enterprise SOAP APIs) then it is not supported on .NET Core. The W stands for Windows after all. However, the ASP.NET Core MVC framework supports Web API and this was originally part of the WCF REST services. Of course, you can still interact with SOAP endpoints (served by various frameworks) as a client, as pointed out elsewhere here.
- vadimberman 9y agoFor me, WCF is the ability to run web services that can be configured on the fly for different protocols, security requirements, etc. It's sad that it won't be available. Honestly, it puts a bit of damper on my development plans.