CoreWCF - What's new and what's next

preview_player
Показать описание
Core WCF is a port of Windows Communication Foundation (WCF) to .NET Core. The goal of this project is to enable existing WCF projects to move to .NET Core. Core WCF provides an upgrade / application modernization path for .NET Framework applications which rely on WCF.

00:00 - What is CoreWCF?
05:30 - CoreWCF Open-source and Roadmap
06:30 - Demo of CoreWCF
15:30 - Future of CoreWCF and wrap-up

#DotNet #CoreWCF #WCF
Рекомендации по теме
Комментарии
Автор

James Montemagno was in Goonies and The Lost Boys as a child actor. Change my mind...

guyincognito
Автор

Hello, what kind of project is the service? Because I see class library and I do not see that you execute it from the Visual Studio.
I need to create a WCF service from scratch with NET 6/7. And I don't see how to do it. thank you

ArielGanc
Автор

I do not think it is matter of wanting to use WCF. It is more a matter of must use WCF. Due to your company policy or, in my case, external company using WCF to communicate with us.

neeftgamer
Автор

great demo, very smart strategy for migration. On that note, would WCF be a good choice for new projects? Or should we stick to REST/gRPC/GraphQL? I am aware that those technologies are not EXACTLY the same as for features, but you can replicate the "Do work" sample using all of them

Qrzychu
Автор

Can we inject dependencies to the Service ? our existing WCF (.net framework 4..6.2) has user management using SQL membership provider. So I am trying to migrate this part to EFCore Identity. So how to inject dependencies like UserManager<IdentityUser> to the service class??
Can we make use of ASP NET Core DI here? if so how?

ssmcs
Автор

Thank you for the demo, I have a question is it possible to perform schema validation on incoming and outgoing messages in CoreWCF?

smartnik
Автор

WCF is soo tied to .net windows, it's really messy to try to make it work with other clients, other platforms, I love wcf but the portability of proto files VS WSDL, and the simplicity of gRPC vs try to figure ut too much details about the channel. make gRPC way to easy and interoperable than WCF. Don't get me wrong. I have many services runing wcf until now, but today we are developing only gRPC services .

sebastianayalavalderrama
Автор

WCF coming back is extremely good news.
Is the old "Dispose() throwing bug fixed in CoreWCF or is it considered a feature now?

Link-hoyq
Автор

hmm, I need to see if this can do web services like .asmx before. I still have some flows that download and upload DataSets.

AdamsTaiwan
Автор

Very important migration. Unfortunately, it is too late.

latala
Автор

Is not bad at all but, why should a company continue developing using WCF when Rest and gRPC are out there?

Aryevang
Автор

how multiple contracts (interfaces) can be used? :)

dario.montoya
Автор

This is great. For companies who have invested a lot of money and time into their products, they can continue moving forwards. Hopefully once the core features have been completed and gets full release with the AWS's support, it will make a lot of people happy.

KibbleWhite
Автор

Do we even need WCF in 2022?
Come on guys don't waste ur time. We already have rest and gRPC

clashclan
Автор

I like the way you did it, without tons of XML in Web.config - just a simple and fluent code. I mean, how often do you have to update your WCF service bindings, transports, security? - Almost never.
With a regular WCF we could also configure services and their bindings from code, however it was cumbersome comparing to what I've seen in this video.
Great job guys

semen-sage