by bill-s, 2019-07-30T04:35:30.836Z
One of the most important new features of .NET Core 3.0 (available now in pre-release and supposed to be released later this year) is its support for gRPC messaging. Wikipedia describes gRPC as follows:
gRPC (gRPC Remote Procedure Calls) is an open source remote procedure call (RPC) system initially developed at Google. It uses HTTP/2 for transport, Protocol Buffers as the interface description language, and provides features such as authentication, bidirectional streaming and flow control, blocking or nonblocking bindings, and cancellation and timeouts. It generates cross-platform client and server bindings for many languages. Most common usage scenarios include connecting services in microservices style architecture and connect mobile devices, browser clients to backend services.
The "killer feature" of gRPC is said to be a support of simultaneous full duplex streaming. HTTP/2 protocol is used for that matter as a transport protocol. Protocol Buffers is used for effective serialization.
As it was said above, .NET Core 3.0 Framework supports gRPC based communication. Visual Studio 2019 offers a boilerplate code for gRPC service. However, this code provides only one-way communication with no message streaming. The project acts as departure point to the current work. In my code, I tried to pick up common code for server and client and combine it to convenient infrastructure that supports bidirectional message streaming with .NET Core 3.0 using gRPC.
by cezarypiatek, 2019-07-30T21:21:30.862Z
How to avoid common mocking issues and save a lot of typing with the help of Roslyn.
by bill-s, 2019-07-30T04:39:34.962Z
Almost any website you visit today is protected by HTTPS. If yours isn’t yet, it should be. Securing your server with HTTPS also means that you can’t send requests to this server from one that isn’t protected by HTTPS. This poses a problem for developers who use a local development environment because all of them run on http://localhost out-of-the-box.
by bill-s, 2019-07-30T04:41:06.428Z
This post of the series digs into the implementation details of the new .NET Core counters.
Part 1: Replace .NET performance counters by CLR event tracing.
Part 2: Grab ETW Session, Providers and Events.
Part 3: CLR Threading events with TraceEvent.
Part 4: Spying on .NET Garbage Collector with TraceEvent.
Part 5: Building your own Java GC logs in .NET
Part6: Spying on .NET Core Garbage Collector with .NET Core EventPipes
by bill-s, 2019-07-30T04:40:26.217Z
This is a "lessons learned" from taking an existing .NET Framework-based REST-ful service and getting it to run under .NET Core in a Docker container.
by bill-s, 2019-07-30T04:36:23.398Z
This Week on Channel 9, Christina is refreshed from Microsoft's internal hackathon and ready to dive into the latest developer news
by bill-s, 2019-07-30T04:37:28.250Z
Microsoft was desperate for relevance in late 1999 at the height of the dot com mania. There were about a dozen technical committees that were supposed to be figuring out the future (the company leaked that Bill was personally chairing the user experience committee) which would be laid out at a press event with the grandiose name of Forum 2000. The committees were pretty much a bust in terms of delivering anything but the company still felt it had to demonstrate it had a future, so there was some furious sausage-making.