Intro to Core WCF In 10 Minutes or Less

[@techdeceptive]

I just loved this 10 MINUTE Session 😍

[@IAmTimCorey]

Great!

[@ezecel9]

Thanks for the video and thanks for speaking slowly and well pronounced. I'm still learning english, but I can understand you very well!

[@IAmTimCorey]

You are welcome.

[@tore28]

It is so annoying Microsoft left WCF behind. The world is not only REST api over HTTPS. WCF supports so many other protocols in addition. For example NetTcp and Msmq. Many developers miss this point.

[@IAmTimCorey]

The problem was that no one else supported WCF. It was a Microsoft-only protocol. Thats why they embraced gRPC. They decided to be industry-standard.

[@Richard-jm3um]

OMG thank you so much for this, just what I needed! :D

[@IAmTimCorey]

You are welcome.

[@mohammednhari1737]

thank you! can i consume an old existing wcf service(not upgraded) from a client application using corewcf?

[@IAmTimCorey]

Yes, I believe you can.

[@mohammednhari1737]

@@IAmTimCorey thanks!! ^^

[@smartnik831]

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

[@scotts6264]

Tim, Do you write Unit Tests for WCF Rest projects?

[@IAmTimCorey]

I haven't built a WCF application in years. I would recommend using unit testing with it, though.

[@scotts6264]

@@IAmTimCorey Hi Tim. would or would not?

[@IAmTimCorey]

Would

[@scotts6264]

@@IAmTimCorey Thanks.Tim. Not sure how to go about it.

[@anaghajahagirdar6515]

Is NamedPipe binding supported in CoreWCF? If not, is there any alternative?

[@IAmTimCorey]

Not sure - you would need to look that up in their documentation.

[@mumk]

i loved the intro

[@IAmTimCorey]

Thanks!

[@ssmcs060]

Oh my God!!!! 😳 I was searching for this word CoreWCF all over KZbin and got only 1 video. Struggling so much all over internet to know about CoreWCF and how to migrate existing net framework WCF projects. Here you upload a video. Great.... Please 🙏🥺 explain how to migrate existing one and how to host on to azure

[@IAmTimCorey]

I don't have enough knowledge of WCF to give you a great explanation of how to upgrade to .NET Core. Sorry.

[@antwanwimberly1729]

Why do we need interceptors ? We can generically handle errors and authentication - authorization

[@yazanshakhshir3049]

Thanks a lot Tim for the great sessions as usual. Can you please explain more about not recommending using this framework with a new project? Did you mean that the person who would use it should have experience in the old WCF , or you don't recommend it at all when the project is new (even if we are familiar with the old WCF) ?

[@IAmTimCorey]

Core WCF is designed to help existing projects in WCF move to .NET Core. It is not recommended for new projects because we have better solutions in .NET Core. For example, gRPC is an open standard that .NET implements. That means that your gRPC service can talk to Java applications, Python applications, and lots more. WCF was proprietary, where the systems in .NET Core (.NET 5+ is .NET Core) focus on industry standards.

[@VaibhavPagare07]

Do you have a full course for this ?

[@IAmTimCorey]

Not on WCF, no.

[@MahmoudSaadawy]

Straight to the point 👌 💯

[@IAmTimCorey]

Thanks!

[@David-rz4vc]

WCF + BlazorWebView = ♥️

[@IAmTimCorey]

Only if it is an existing project, though. Otherwise, I would recommend gRPC or API instead of WCF.

[@andywalter7426]

In around 2014, I found wcf useless. Before 2014, I used wcf for the apis. However, eventually, visual studio had no support anymore for creating the clients for mobile devices (including at that time windows phones). At that time, I found out about web api and saw I was able to build my own clients. So I went with web apis and no regrets (and now even minimal apis). I found it very easy to move from wcf to web api. I think companies should have just moved to web api. I found that everything you can do in wcf, you can do in web api plus web api is much more flexible and more easily work on more platforms.

[@IAmTimCorey]

It doesn't sound like you actually used WCF for very much. Yes, it can do request/reply JSON communication like an API. However, the reason why people are still on WCF and haven't moved to API is because WCF can also do binary communication, one way communication, duplex message exchanges, TCP communication, MSMQ, and a LOT more that API cannot do. gRPC replaces some of it with its ability to stream data, but it is still HTTP and not TCP or other. Companies cannot "just move" to API. That's like saying that people who own a truck should just use a car. If they are using the truck just for passengers, that might work, but if they were using the truck to haul appliances or other large items, that won't work.

[@terry.chootiyaa]

*Can you sum-up ..what can, .net framework and c, cpp, c# do better then other frameworks on Linux ?* 😐

[@IAmTimCorey]

You want to know why you should use C# on Linux. Is that correct?

[@terry.chootiyaa]

@@IAmTimCorey *No what I mean is what is the reason .net is used over other frameworks like django and others, we're less code is needed to accomplish the same results ....the way I see it is ...the less code used the more reliable the app.* 😊👍

[@suikast420]

Yeah grcp is fine but thats not the same as wcf. I have used WCF before 6 years and would ever use if I can. ( I must live with java projects ). A pitty that the concepts of WCF does not beacame a standard like grpc.

[@IAmTimCorey]

I get it. Unfortunately, you just highlighted the issue - since you are on Java, you can't use WCF. That was the problem. If you didn't use C#, you couldn't use WCF. With gRPC, you can use it on Java, JavaScript, C#, and LOTS more.

[@suikast420]

@@IAmTimCorey indeed. I know. What I want to point to is the concept of WCF. You can use the same service with in mem in proc over system oscket and over network. Without changing or gerenrating new stuff. That is the point. On the otherhand I like gRPC.

[@markroworth5700]

You haven't actually said what it does.

[@IAmTimCorey]

WCF is a communications technology that was used in the .NET Framework. It has been deprecated by Microsoft, but resurrected enough to port your WCF projects to .NET Core by the community. Basically, if you aren't already familiar with WCF, you don't need to worry about the Core version. It is only for those who want to upgrade. We have better options in .NET Core like gRPC.

[@terry.chootiyaa]

*CORE WCF ...."What Came First" is this like the chicken and egg thing 😐*

[@IAmTimCorey]

Huh? I'm not sure what you are saying.

[@ssmcs060]

Ohhh 😢!!! Only this much in bideo. Intro video 😢. Please 🥺 explain how to migrate existing WCF having EF, Azure storage related operations, SQL database, identity, etc to CoreWCF...

[@PaulSebastianM]

Lol you're funny...

[@IAmTimCorey]

That’s a pretty specific scenario and not likely to be covered here. Sorry.

[@XKS99]

WE NEED RELIABLESESSIONS GODDAMMI**T

[@marccru5702]

You added literary nothing to the table, the people that come to this vide know what CoreWCF is, they need to learn to migrate. What a waste of 10 min. 4:31.

[@IAmTimCorey]

This was titled “Intro to Core WCF”, not “How To Migrate WCF”. That would be a different video and definitely not ten minutes if it were to be helpful at showing migrations.

[@BeNetCoders]

@@IAmTimCorey I wanted to know what WCF was, so this we perfect. Thanks allot for your time. 😊👍

[@terry.chootiyaa]

@IAmTimCorey *No what I mean is what is the reason .net is used over other frameworks like django and others, we're less code is needed to accomplish the same results ....the way I see it is ...the less code used the more reliable the app.* 😊👍

[@IAmTimCorey]

Picking the language that uses the least number of lines of code isn't a great way to decide things. For example, you can build a fully functional API with full data access in C# in less than 30 lines of code. That's not the point of writing code. The point is to have readable, easily maintainable code. Code is meant to be read by humans. That means you should be taking that into account as one of the biggest factors. Fewer lines of code sounds good, but in reality it just means you are either hiding more of the actual implementation details or you are squishing things together too much. Pick the language that works best for your team, that you know the best, and that best supports the wide range of projects you need to do with it. That's why C# is so popular - you can use the same code to build applications on almost any platform.