Last post Feb 03, 2021 03:51 PM by bruce (sqlwork.com)
May 23, 2020 01:48 PM|omsaisaanvi|LINK
i am migarting asp.net project to ,net core 3.1
how to migrate wcf here , shall i migrate wcf or use rest api for this or any other better suggestion
May 23, 2020 02:18 PM|lextm|LINK
May 25, 2020 09:08 AM|Sherry Chen|LINK
Hi omsaisaanvi ,
Read the following link which is helpful
Jun 01, 2020 06:10 PM|yogyogi|LINK
Since you are using ASP.NET Core 3.1 version so gRPC will be a perfect choice. Here is the
Implementation of gRPC in ASP.NET Core article.
Jun 01, 2020 08:01 PM|bruce (sqlwork.com)|LINK
while gRPC is a great library, typically faster than REST, and a contract based replacement for WCF, it has some restrictions. it requires HTTP/2 so it not callable from a browser (ajax). Also legacy systems may not be able to call it either.
as always, you should define your requirements, before picking a technology.
Feb 02, 2021 08:20 PM|omsaisaanvi|LINK
Requirement is wcf is getting use in project but lots of wcf attribute like contract , servicehost all comes under system.servicemodel which is deprecated in .net core
Feb 03, 2021 03:51 PM|bruce (sqlwork.com)|LINK
Requirements would include the calling clients. What technology do they support? Also any network restrictions? Is contract support required? What security is required?
Webapi REST or GraphQL are the .net core replacements for wcf, but do not include contract or binary support. While not supported by default, xml can be added to webapi. gRPC is open source and has more wcf features but requires http/2 support by the server
and the calling clients.
I typically use webapi REST with swagger. the swagger support gives a client code generator and documentation