I remember 15 years ago WCF and SOAP was the next big thing and at some point around 2012 REST was considered "the way" to get around all the complexity (which in many ways it did) and now we are back to where we started with gRPC. This is nuts. Nice course though... I do learn a lot from your courses and appreciate the effort.
Well, REST is still a thing and gRPC won't replace it (I don't think) because of how simple it is. gRPC, though, will definitely be a major player for a while yet, since it is so fast and versatile. The biggest thing going for it, though, is the fact that it is an industry standard instead of a Microsoft-specific product.
I made another Tutorial before (where I had to read off the website) and it was a whole lot more complicated. It didn't really start from scratch anyways and never said anything about rebuilding. Instead there was a .bat file you had to run, which didn't really do the job. Anyway I braced myself and looked for a video tutorial. That usualy does it better for me anyways. Thinking it's gonna be complicated, and the Tutorial will take 1h raw video material, I was pretty surprised when I had a "Hello Linkario" coming back at me after about 28 Minutes. Thanks a lot, great tutorial and very well explained
thx Corey, you really helped us out a lot in getting to understand gRPC since for students it's not the most ez task to fullfill. Hope you stay as amazing as you are, Greetings Max
I barely known about this new technology because of some .NET Conferences, but now it is more clear to me to understand what is it all about, thank you Tim.
Great tutorial for beginning. thanks a lot. Specially appreciate the last part where you talk about when you should use GRPC, because I hear a lot from people to replace API with GRPC with no solid reason
Awesome tutorial, straight to code and good info along the way. Next thing would be find some good design patterns around gRPC that can help convert a large WCF service.
Thanks Tim. As always it is clear and nice presentation. GRPC reminds me WCF somehow. I think it is nice for mircoservices architecture. Because the communication should be as fast as possible and probably closed for connections from outside of the solution. Another point is streaming. It reminds me a short time subscription. Let’s assume we have a client which should receive some messages from a server. So it should establish a connection to server 1st and then some notifications keep arriving till a client keeps connection open. I think it can be useful feature. Thanks again Tim.
Great video, thanks, Tim! Any new C# related technology I'm exploring I now search your videos before even googling! I'm exploring gRPC for local IPC which I think is an exciting and appropriate application.
I like the fact you don't (and shouldn't) need to aggregate a huge amount of data on the server side if you want to return it. Just loop on each record and return them as you enumerate them.
@@IAmTimCorey But sooner or later the streaming server has to say "its all, I am done with the data stream". And point is, THIS client is blocked (cannot send anything else) until the "end" flag comes from the server. You haven't mention this in the video. Or you mean, that the exit from the sending function on a server side automatically closes the stream?
Projects/people started using it, I went to an interview and I said I've heard of it. A gen Y, generously put a "1" next to my knowledge. I might get a 2+ now!
I will be using this in a stand alone server service. I will accept calls from my client to perform batch work which runs separately from the client computers. I don't want to rely on IIS or I would use WebAPI.
Nice intro! I was on the verge of trying to port our WCF comm at work to gRPC, but after seeing your vid. I think it won't be that easy as I thought. We are using bi-directional channels for notifications and also file streaming with continuation (when communication drops and whole call timeouts, it can continues with the next call where it left off).
I'm glad it was valuable to you, even if it showed you that you have more work to do. There is a possible port of WCF to .NET Core in the works. That might be a better option (but it is a ways off from production-ready).
Well, the move to .NET Core is what killed WCF (Microsoft didn't see the value in porting it). The good news is that Microsoft turned over the source code for WCF to the community so that it can be ported by those who still want to use it. Hopefully you gain back WCF at some point.
@@IAmTimCorey Wow, a reply from Mr Tim himself. I am honored! But anyway, only WCF Client is open source. The WCF Server, Servicehost and even WCF Web is not. For guys who build their entire stack with WCF, it's not only a hard migration, but doesn't make sense from a business point of view too.
A good use for this would be SCADA where equipment that needs to be monitored can run a tiny gRPC server in it's own ARM system (like IOT devices, but for industrial control). I wish we had this 30 years ago. This is cool - I'm going to surf for some Arduino projects to see if any use gRPC ;) *** update- yes there are quite a few Arduino gRPC server projects/libraries. This will be fun! ***
Hey Tim great video. Easy to understand. I watched it to the end, but I have one major complaint: you saved the “when would you use this” for the very end, which I felt was a bad move because essentially you said “you wouldn’t”. Kind of a huge let down.
I understand what you are saying, but I think you missed what I said at the end. I didn't say you wouldn't use gRPC. I said you wouldn't use it often. There's a big difference. I said that it is a great tool to have in your toolbox. I also said that gRPC is valuable when you need speed or when you need to stream data. The reason I saved the "when would you use this" until the end is because that section relies on you understanding what gRPC is in order to understand the points I was making. Otherwise, you might just ignore the technology because you mistakenly thought I said it wasn't useful. Then when a situation comes up where it would be a perfect fit, you won't know to use it.
Nice course, one small suggestion unless you see an obvious no-no... When adding the proto file to the client, might suggest a little alternative. Create the folder as suggested in the video, but now use "Add Existing" to the "Clients\Protos" folder. Now navigate to the "ClientDemo\Proto" folder in the Demo project, you'll need to change the filespec in the add item dialog to all files i.e. "*.*" now select the greet.proto files but now the catch... On the Add button you'll see a chevron click on it NOT "Add", now use "Add Link". Now we only have one copy and the client will be updated and you only need to worry about one copy of the proto file being defined and it should alwa
Yes, if I were creating this for production use, I would make sure that my proto files were shared so that I don't have to update them both when a change gets made. However, I was trying to simulate what you would do when you don't control the client or the server.
@@IAmTimCorey Does it make sense to create a class library project that's being referenced in both the server and the client projects and put the proto files there? If not, what could go wrong?
I spent a lot of time implementing gRPC in a program, and I think I'll be scraping it. There are many things I don't like. It's too difficult to keep everything in sync. There are no tools to convert classes to proto files, which is a problem if you have a lot of classes. Solely using classes from a class library that you may not control doesn't make that any easier. It's cumbersome to map properties of an instantiated class to that of a proto. And perhaps the biggest issue of all, proto3 does not support null properties. Properties which are null get a default value. I'm glad that I learned a new thing, but I don't think I'll ever use it.
ok from what I see the way you set it up looks like good old SOAP Web Services. although it's a lot more efficient than sending and receiving XML data I really like it. but I really got a question. from what I saw ". proto" files are simply plain text files and everyone can forge them and I don't see a signature or encryption. how do you protect these services from unauthorized or malicious access? do I implement my own authentication and authorization method (for instance maybe issuing, sending, and validating a JWT for the input of services?) or there is a standard way of implementing authentication and authorization in GRPC?
I like your very good example of GRPC services, and sending lists also seems to me to be a very good video, but will you have an example where you can receive two lists in the service? Excuse my English which is not my native language, I will be very grateful if you could guide me.
Awesome video Tim, as usual, I have a question: Can I use a gRPC as service to be consumed by a frontend app ??? The scope of this kind of services is only for backend ??? Thanks in advance !
I found a strange bug in VS2019 with the .proto Build Action. When you make changes to an existing proto file (or copy it over from the server to the client), VS may leave a bunch of red squiggly lines from the "using GrpcServer" and elsewhere in your client program.cs file. The solution was to change the Build Action from Protobuf to None, then save, then change None back to Protobuf again (go figure). I'm using DotNet5 to follow this tutorial (great tutorial, by the way. Thanks!) and it's pretty much working correctly - same with the "Client only" part - they fixed that bug.
Hello Tim, I try to run the Grpc server and the client, I get the following error. Grpc.Core.RpcException: 'Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: The SSL connection could not be established, see inner exception. AuthenticationException: The remote certificate is invalid according to the validation procedure.", TIA.
Would it not make sense to create a shared library for the protobufs? This way the 'contract' between the client and server are truly shared and you wouldn't need to copy/paste.
Thanks also for explaining when to use gRPC Vs Web API. A year later, after GA of .NET 5 and a more robust implementation of gRPC on .NET 5 things are still the same or the field of application of gRPC has expanded?
gRPC has definitely expanded and become a great option in certain circumstances. It is still not a replacement for an API, but it definitely has a place of its own.
Hi Tim; Thanks for this great course. I'd like to make a suggestion. You had made an offer to those who are Patreon (with >$10 Level) with the Tips & Tricks. The problem is that, the notion of Patreon has become overly used by so many developers and people that is hard to get involved with a Patreon with someone, just because you need a source code or a tip sheet and etc. Next thing you know, you're paying a bunch of money every month where you're not using anything. Because of this, I see less and less people get involved in Patreon unless, they're using the product on daily basis. My suggestion is create your tip sheet or source code or whatever you have and sell it in your store AS IS with one purchase, rather asking people to commit to monthly payment. Imagine you go buy a pair of shoes and store owner says, you have to pay $10 per month for one year. To consumer if feels they're getting locked down. But if he says, it's price is $120, it's much easier for that consumer to pay $120 and walk out being free. Give us a price for the Sheet/Tip sheet. If it sounds fair, we'll buy it. Hope this helps!
Think of gRPC like any other data access. What you have seen in this video can be replicated in a class library. Then you can connect that class library to any front-end, including ASP.NET Core 5.
first i create console app, but then my customer ask me to provide grpc service. i try to host grpc server in my console app but how can i change the port for grpc server? i stuck on this.
Hi Tim, I really like your channel. Although I am watching this video for the. first time, it seems that gRPC is going to be used to replace WCF at some point in .Net Core. It is much like WCF with capabilities beyond what WCF can do. I agree that it should be used only when needed just as WCF. You still have services and contracts like WCF has but in an industry standard across all platforms and languages as you stated. As you said, web apps would be a much better solution. Thanks for the great lessons.I look forward to learning more on your channel.
Also for me gRPC was something unknown. Thanks. PS: in the past I had the same problem with freezing .net Core console by accidentally clicking it. You must remove "Quick Edit Mode" from "Command Prompt" Properties
Yeah took me a while to figure that out. It's when you select something in the console, then it pauses the execution. If you hit enter in the console it resumes the execution.
Hi Tim, as usual great stuff. Just one question: I need to build a system where there are one or more servers which are connected to hardware devices which stream bytes to the server/s and that stream of bytes needs to be sent to the client to do some processing with the data. So, is gRPC a good choice for such a scenario? The data is sent in packets of 1KBytes at most to the server.
thank you for your Answer last time, I solved the problem by writing some code in program.cs in the Server Side, and writing some come in the client-side too, server-side code: in program.cs webBuilder.ConfigureKestrel(options=>{ options.ListenLocalhost(5001, o => o.Protocols = Microsoft.AspNetCore.Server.Kestrel.Core.HttpProtocols.Http2); }); client side program.cs AppContext.SetSwitch("System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport", true);
Hey. Could you make an updated version for this? In Visual Studio 2022 there aren't any of these properties for greet.proto client even though i copy paste it from a server
Sorry, I am not Tim, but I am pretty confident that it wont. At least not in any foreseeable future. Replacing technology isn't just about having something smarter (if that was the case, JavaScript would be long gone). It is, more or less, about everything else. There are so many services working over HTTP already and so many developers used to HTTP, you don't just change the direction of that ship. It's not that I don't think gRPC is clever, it's just that I think that the world is already so locked on HTTP, that won't just go away.
@@Noceo I fully agree... Here is where I think gRPC fits well; Suppose a company is building an application that requires both the serve and client the team has full control of both ends. Here gRPC offers a better and faster transport system than HTTP. Suppose you write a Blazor client where you also need data from server, where you build your server to get/set data from/to client, I'd use gRPC than Web API, especially if you need secure and fast transport. I'm now investigating into this.
I'm a little confused. You used "package" in the first proto file, but not the customer proto file, so when I replayed the section where you describe the proto file, you say the package is the name of the package ... but what is package actually used for?
4 years later and still helpful... Thank you Tim, very much appreciated!
You are welcome.
Usually i don't watch long videos but after this i found that i'm missing a lot info in short videos. Thanks A lot 🌺🌺
Excellent!
try replay speed 1.25 :)
I remember 15 years ago WCF and SOAP was the next big thing and at some point around 2012 REST was considered "the way" to get around all the complexity (which in many ways it did) and now we are back to where we started with gRPC. This is nuts. Nice course though... I do learn a lot from your courses and appreciate the effort.
Well, REST is still a thing and gRPC won't replace it (I don't think) because of how simple it is. gRPC, though, will definitely be a major player for a while yet, since it is so fast and versatile. The biggest thing going for it, though, is the fact that it is an industry standard instead of a Microsoft-specific product.
Your skill to explain the theme is so good! Thank you! And I am not a native English speaker.
Thank you!
I don't how to get started with gRPC until I see this video. Highly appreciate your effort, sir.
I am glad it was so helpful.
I made another Tutorial before (where I had to read off the website) and it was a whole lot more complicated. It didn't really start from scratch anyways and never said anything about rebuilding. Instead there was a .bat file you had to run, which didn't really do the job.
Anyway I braced myself and looked for a video tutorial. That usualy does it better for me anyways. Thinking it's gonna be complicated, and the Tutorial will take 1h raw video material, I was pretty surprised when I had a "Hello Linkario" coming back at me after about 28 Minutes.
Thanks a lot, great tutorial and very well explained
I am glad it was helpful.
thx Corey, you really helped us out a lot in getting to understand gRPC since for students it's not the most ez task to fullfill. Hope you stay as amazing as you are,
Greetings Max
Thanks for watching and trusting Tim to help expand your skills
0:00 - Intro
2:31 - Creating Demo gRPC app
4:13 - gRPC app template overview
17:48 - Creating gRPC Client console app
28:59 - Custom gRPC Service
45:23 - Updating gRPC Service: streaming multiple data sets to client
58:26 - When to use gRPC, summary and concluding remarks
Thank you!
Really, you're the best teacher!
Thank you!
Needed to learn GRPC for a project at work. Nice tutorial! Thanks.
You are welcome.
Very well explained. Easy to understand. Thanks
You are welcome!
I barely known about this new technology because of some .NET Conferences, but now it is more clear to me to understand what is it all about, thank you Tim.
Excellent!
Wow, great video! I'm gonna share this with my team.
Great!
Thank you so much for your awesome explanations of a very complicated topic, Mr. Corey!
You are welcome.
Tim, at 16 minutes you explained the thing that's been battering my brain for 3 days. Talk about obtuse.
Thanks for the video. Very helpful
Glad it helped!
This was fantastic!
Thank you!
Love the thorough and paced explanations! Very beginner friendly!
Glad it was helpful!
We need a Thank You Tim Corey T-shirt.
Fan produced merchandise! Love it. Where do I purchase?
Hi Tim, Wonderful way of explaining things and really worth content.
Thank you!
Your a legend Tim!
Thanks!
Great tutorial for beginning. thanks a lot.
Specially appreciate the last part where you talk about when you should use GRPC, because I hear a lot from people to replace API with GRPC with no solid reason
Thanks for trusting Tim
Awesome tutorial, straight to code and good info along the way. Next thing would be find some good design patterns around gRPC that can help convert a large WCF service.
I will add it to the list. Thanks for the suggestion.
In Tim Corey we trust!
God is a better to focus on and trust. I promise.
Good stuff. Looking forward to see how grpc support dev documentation like openAPI
Thank you. We appreciate you sharing.
Thanks Tim. As always it is clear and nice presentation. GRPC reminds me WCF somehow. I think it is nice for mircoservices architecture. Because the communication should be as fast as possible and probably closed for connections from outside of the solution. Another point is streaming. It reminds me a short time subscription. Let’s assume we have a client which should receive some messages from a server. So it should establish a connection to server 1st and then some notifications keep arriving till a client keeps connection open. I think it can be useful feature. Thanks again Tim.
Yep, it has similar characteristics of WCF.
@@IAmTimCorey what do you think about notifications? Is it good idea to use gRPC to inform a client based on events happened on server side ?
Great video, thanks, Tim! Any new C# related technology I'm exploring I now search your videos before even googling!
I'm exploring gRPC for local IPC which I think is an exciting and appropriate application.
I am glad my content is so helpful.
Here you are where HOW TO GET STARTED has it's meaning.. great thanks.
You're very welcome
I like the fact you don't (and shouldn't) need to aggregate a huge amount of data on the server side if you want to return it. Just loop on each record and return them as you enumerate them.
Yep, that can be pretty powerful.
@@IAmTimCorey But sooner or later the streaming server has to say "its all, I am done with the data stream". And point is, THIS client is blocked (cannot send anything else) until the "end" flag comes from the server. You haven't mention this in the video. Or you mean, that the exit from the sending function on a server side automatically closes the stream?
@@MrDimonsky Yes, the sending function needs to call onComplete() when it is done with the data which initiates a half-close for the stream.
Wow, I didn't even know this existed. Thanks
You’re welcome.
Projects/people started using it, I went to an interview and I said I've heard of it. A gen Y, generously put a "1" next to my knowledge. I might get a 2+ now!
I haven't seen the word "Marshaller" since i was reading a COM+ book.
It isn’t something you use a lot, for sure.
Exactly what I was looking for
Excellent!
Thanks Tim! This was really helpful, i now know what the other guys are talking about for the future of our application.
Glad it was helpful!
Really interesting. Contract based and performant.
Thanks!
Seems like every decade or so, there's a "latest and greatest" way to do rpc. What happened to SOAP and WSDL? I'm getting too old for this. Lol.
lol
The book and workshop selers had sold all they where able to sell :)
It's madness. I swear Microsoft is devolving.
And blazor is just fancy asp.net webforms with server side handlers
gRPC is a potential replacement for SOAP.
I watched this and built the sample along side you because the Anki Vector Robot uses gPRC and I wanted to get a better understanding. Thanks!
Great!
TIM Thanks once again for this beautiful explanation.
You are welcome.
I will be using this in a stand alone server service. I will accept calls from my client to perform batch work which runs separately from the client computers. I don't want to rely on IIS or I would use WebAPI.
Good to know.
Hello Tim.
Thanks for the great courses.
Can you make a tutorial for SignalR?
Sometimes it is really needed.
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
Again another good explanation for which I was looking for.
Great!
Hello Tim, Great video! I will share with my squad. Thanks.
You are welcome.
@@IAmTimCorey Thanks!
Nice intro! I was on the verge of trying to port our WCF comm at work to gRPC, but after seeing your vid. I think it won't be that easy as I thought. We are using bi-directional channels for notifications and also file streaming with continuation (when communication drops and whole call timeouts, it can continues with the next call where it left off).
I'm glad it was valuable to you, even if it showed you that you have more work to do. There is a possible port of WCF to .NET Core in the works. That might be a better option (but it is a ways off from production-ready).
Great work man, thanks for your tutorials!
You are welcome.
66K and going hard! GRPC... you killed my beloved WCF!!
Well, the move to .NET Core is what killed WCF (Microsoft didn't see the value in porting it). The good news is that Microsoft turned over the source code for WCF to the community so that it can be ported by those who still want to use it. Hopefully you gain back WCF at some point.
@@IAmTimCorey Wow, a reply from Mr Tim himself. I am honored! But anyway, only WCF Client is open source. The WCF Server, Servicehost and even WCF Web is not. For guys who build their entire stack with WCF, it's not only a hard migration, but doesn't make sense from a business point of view too.
as always well explained well gone thru, i know now much more than before
Excellent!
Great tutorial, Thanks Tim
You are welcome.
Very good tutorial style.. Enjoyed it.
Thank you!
Thanks for this great introductory video... Appreciated
You are welcome.
Thanks a lot, it saved my work today.
Awesome!
Thanks Tim, very kind!
You are welcome.
This was a great video as always. Anyone know of any gRPC tutorials specifically covering authentication techniques?
Thank you!
From the beginning I had this idea that this should be the right tool for microservice communications.
It depends on the situation but this is a nice option. Queues are another great option if you don’t need real-time data.
Thanks Tim! It's very well structured and a great quick start tutorial :)
You're very welcome!
Thanks Tim this was really good.
Thank you!
superb content. Thanks for the intro to Grpc.
You are welcome.
I subscribed immediately. Very clear and easy to follow.
your videos are gold
Thanks
Amazing, Good Job Corey!
Thanks!
A good use for this would be SCADA where equipment that needs to be monitored can run a tiny gRPC server in it's own ARM system (like IOT devices, but for industrial control). I wish we had this 30 years ago. This is cool - I'm going to surf for some Arduino projects to see if any use gRPC ;) *** update- yes there are quite a few Arduino gRPC server projects/libraries. This will be fun! ***
Great!
Thanks! (Dolar tax down here in Brazil are very high for us at this moment)
Thank you!
gRPC for microservices built in Node js works really well!
Glad you like it.
Thanks Tim. This was a great video!
Glad you enjoyed it!
Fantastic video. I have learned alot.
Great!
Great video. Good start. Keep rocking.
Thanks!
He said: "well that's just awesome' and I spit up my pop. I have been there so many times. LOL!
lol we all have.
Hey Tim great video. Easy to understand. I watched it to the end, but I have one major complaint: you saved the “when would you use this” for the very end, which I felt was a bad move because essentially you said “you wouldn’t”. Kind of a huge let down.
I understand what you are saying, but I think you missed what I said at the end. I didn't say you wouldn't use gRPC. I said you wouldn't use it often. There's a big difference. I said that it is a great tool to have in your toolbox. I also said that gRPC is valuable when you need speed or when you need to stream data.
The reason I saved the "when would you use this" until the end is because that section relies on you understanding what gRPC is in order to understand the points I was making. Otherwise, you might just ignore the technology because you mistakenly thought I said it wasn't useful. Then when a situation comes up where it would be a perfect fit, you won't know to use it.
Nice course, one small suggestion unless you see an obvious no-no... When adding the proto file to the client, might suggest a little alternative. Create the folder as suggested in the video, but now use "Add Existing" to the "Clients\Protos" folder. Now navigate to the "ClientDemo\Proto" folder in the Demo project, you'll need to change the filespec in the add item dialog to all files i.e. "*.*" now select the greet.proto files but now the catch... On the Add button you'll see a chevron click on it NOT "Add", now use "Add Link". Now we only have one copy and the client will be updated and you only need to worry about one copy of the proto file being defined and it should alwa
Yes, if I were creating this for production use, I would make sure that my proto files were shared so that I don't have to update them both when a change gets made. However, I was trying to simulate what you would do when you don't control the client or the server.
@@IAmTimCorey Does it make sense to create a class library project that's being referenced in both the server and the client projects and put the proto files there? If not, what could go wrong?
I spent a lot of time implementing gRPC in a program, and I think I'll be scraping it. There are many things I don't like. It's too difficult to keep everything in sync. There are no tools to convert classes to proto files, which is a problem if you have a lot of classes. Solely using classes from a class library that you may not control doesn't make that any easier. It's cumbersome to map properties of an instantiated class to that of a proto. And perhaps the biggest issue of all, proto3 does not support null properties. Properties which are null get a default value. I'm glad that I learned a new thing, but I don't think I'll ever use it.
Unless you really need the streaming or the extra bit of speed, it sounds like an API might be a better solution for you.
Can you make a video about how we can maintain versions in gRPC?
Added to the suggestions list, thanks
ok from what I see the way you set it up looks like good old SOAP Web Services. although it's a lot more efficient than sending and receiving XML data I really like it. but I really got a question. from what I saw ". proto" files are simply plain text files and everyone can forge them and I don't see a signature or encryption. how do you protect these services from unauthorized or malicious access? do I implement my own authentication and authorization method (for instance maybe issuing, sending, and validating a JWT for the input of services?) or there is a standard way of implementing authentication and authorization in GRPC?
Excellent stuff.
Thanks!
I like your very good example of GRPC services, and sending lists also seems to me to be a very good video, but will you have an example where you can receive two lists in the service?
Excuse my English which is not my native language, I will be very grateful if you could guide me.
I don't have an example of that. Look into the documentation at docs.microsoft.com for more information and examples.
Very useful explanation. Thanks
You are welcome.
This is better at 1.25 speed.
It all depends on your listening comprehension. I personally like 1.5x.
@@IAmTimCorey Yes, but you remind me of Matthew Santoro at 1.25, at 1.5 it sounds like a squeaky mouse voice.
Thanks, simple & nice explanation.
Glad it was helpful!
Awesome video Tim, as usual, I have a question: Can I use a gRPC as service to be consumed by a frontend app ??? The scope of this kind of services is only for backend ??? Thanks in advance !
Yes you can.
I found a strange bug in VS2019 with the .proto Build Action. When you make changes to an existing proto file (or copy it over from the server to the client), VS may leave a bunch of red squiggly lines from the "using GrpcServer" and elsewhere in your client program.cs file. The solution was to change the Build Action from Protobuf to None, then save, then change None back to Protobuf again (go figure). I'm using DotNet5 to follow this tutorial (great tutorial, by the way. Thanks!) and it's pretty much working correctly - same with the "Client only" part - they fixed that bug.
I'm glad you figured it out. It would be good to submit this bug so that you know someone is working on a fix.
Hello Tim,
I try to run the Grpc server and the client, I get the following error.
Grpc.Core.RpcException: 'Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: The SSL connection could not be established, see inner exception. AuthenticationException: The remote certificate is invalid according to the validation procedure.",
TIA.
Would it not make sense to create a shared library for the protobufs? This way the 'contract' between the client and server are truly shared and you wouldn't need to copy/paste.
Usually but I didn’t want to imply that is the only way to do it.
great explanation
Thanks!
Thanks for this video. I guess, now with C# 8, we can use much better IAsyncEnumerables with streams.
Yep
await foreach (var currentCustomer in call.ResponseStream.ReadAllAsync())
{
Console.WriteLine($"{currentCustomer.FirstName} {currentCustomer.LastName}: {currentCustomer.EmailAddress}");
}
GREAT Video .. Learned A LOT . Thank you sooo Much
Excellent!
Hi.
Should be nice seeing the process of publishing production enviroment!
I will add it to the list. Thanks for the suggestion.
Thanks! Great, as always!)
You are welcome.
Thanks also for explaining when to use gRPC Vs Web API. A year later, after GA of .NET 5 and a more robust implementation of gRPC on .NET 5 things are still the same or the field of application of gRPC has expanded?
gRPC has definitely expanded and become a great option in certain circumstances. It is still not a replacement for an API, but it definitely has a place of its own.
Very interesting. Thanks Tim.
You are welcome.
Hi Tim;
Thanks for this great course. I'd like to make a suggestion. You had made an offer to those who are Patreon (with >$10 Level) with the Tips & Tricks. The problem is that, the notion of Patreon has become overly used by so many developers and people that is hard to get involved with a Patreon with someone, just because you need a source code or a tip sheet and etc. Next thing you know, you're paying a bunch of money every month where you're not using anything. Because of this, I see less and less people get involved in Patreon unless, they're using the product on daily basis.
My suggestion is create your tip sheet or source code or whatever you have and sell it in your store AS IS with one purchase, rather asking people to commit to monthly payment.
Imagine you go buy a pair of shoes and store owner says, you have to pay $10 per month for one year. To consumer if feels they're getting locked down. But if he says, it's price is $120, it's much easier for that consumer to pay $120 and walk out being free.
Give us a price for the Sheet/Tip sheet. If it sounds fair, we'll buy it.
Hope this helps!
I'll take that suggestion and consider it. Thanks!
Thank you for the introduction video... Could you please explain how to connect with client UI with Asp.Net 5.0?
Think of gRPC like any other data access. What you have seen in this video can be replicated in a class library. Then you can connect that class library to any front-end, including ASP.NET Core 5.
first i create console app, but then my customer ask me to provide grpc service. i try to host grpc server in my console app but how can i change the port for grpc server? i stuck on this.
Hi Tim, I really like your channel. Although I am watching this video for the. first time, it seems that gRPC is going to be used to replace WCF at some point in .Net Core. It is much like WCF with capabilities beyond what WCF can do. I agree that it should be used only when needed just as WCF. You still have services and contracts like WCF has but in an industry standard across all platforms and languages as you stated. As you said, web apps would be a much better solution. Thanks for the great lessons.I look forward to learning more on your channel.
You are welcome.
Great video Tim, thank you so much. A question, what do you recommend to "wrap" existing REST API services to use gRPC?
I don't recommend doing that except in very specific circumstances. Otherwise you have the worst of both worlds.
Also for me gRPC was something unknown. Thanks.
PS: in the past I had the same problem with freezing .net Core console by accidentally clicking it. You must remove "Quick Edit Mode" from "Command Prompt" Properties
Thanks for sharing. I’ll try that out.
Yeah took me a while to figure that out. It's when you select something in the console, then it pauses the execution. If you hit enter in the console it resumes the execution.
Or just hit Esc will do
Very insightful!! Subscribed!!
Thank you.
The gRPC the future for the web call, faster and faster
gRPC is a good option for some situations.
Hi Tim, as usual great stuff. Just one question: I need to build a system where there are one or more servers which are connected to hardware devices which stream bytes to the server/s and that stream of bytes needs to be sent to the client to do some processing with the data. So, is gRPC a good choice for such a scenario? The data is sent in packets of 1KBytes at most to the server.
Probably. The client will need to implement the gRPC contract, but gRPC is designed to do streaming in two directions (if needed).
thank you for your Answer last time, I solved the problem by writing some code in program.cs in the Server Side, and writing some come in the client-side too,
server-side code: in program.cs
webBuilder.ConfigureKestrel(options=>{
options.ListenLocalhost(5001, o => o.Protocols = Microsoft.AspNetCore.Server.Kestrel.Core.HttpProtocols.Http2);
});
client side program.cs
AppContext.SetSwitch("System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport", true);
Thanks for sharing!
Thank you sir for this gread video.
You are welcome.
Hey. Could you make an updated version for this?
In Visual Studio 2022 there aren't any of these properties for greet.proto client even though i copy paste it from a server
Very nice and clear tutorial.. thx..
You are welcome.
Tim, do you think gRPC will replace ASP.NET Web API Core as RESTful service for the .NET world?
Sorry, I am not Tim, but I am pretty confident that it wont. At least not in any foreseeable future. Replacing technology isn't just about having something smarter (if that was the case, JavaScript would be long gone). It is, more or less, about everything else. There are so many services working over HTTP already and so many developers used to HTTP, you don't just change the direction of that ship. It's not that I don't think gRPC is clever, it's just that I think that the world is already so locked on HTTP, that won't just go away.
@@Noceo
I fully agree...
Here is where I think gRPC fits well; Suppose a company is building an application that requires both the serve and client the team has full control of both ends. Here gRPC offers a better and faster transport system than HTTP.
Suppose you write a Blazor client where you also need data from server, where you build your server to get/set data from/to client, I'd use gRPC than Web API, especially if you need secure and fast transport.
I'm now investigating into this.
Thank you very much, is there a way to still get the cheat sheet?
I do not believe so, no.
I'm a little confused. You used "package" in the first proto file, but not the customer proto file, so when I replayed the section where you describe the proto file, you say the package is the name of the package ... but what is package actually used for?