The Microsoft Graph SDK for .NET provides a pleasant experience for working with the Microsoft Graph APIs. However, what if you wanted more control over how the underlying HTTP pipeline is used? In this episode, Darrel Miller comes on to show us all how to make use of the various options for customizing the HTTP pipeline for sending and receiving information with the Microsoft Graph SDK for .NET. [01:00] - Overview of options for using the Graph SDK[02:36] - Visualizing the Graph SDK architecture[05:25] - Customizing the underlying HttpClient (Demo)[09:59] - Customizing the pipeline with DelegatingHandlers (Demo)[14:59] - Customizing individual requests (Demo) Useful LinksAuthentication with Graph SDKsMicrosoft Graph Dev CenterMicrosoft Graph ExplorerMicrosoft Graph on GitHub

To call into Microsoft Graph, your code must acquire an access token from the Microsoft identity platform. To get an access token, your app must be registered and authorized with the Microsoft identity platform. In this episode, Darrel Miller joins Christos to show us all how to make authorized requests with the Microsoft Graph SDK within our .NET applications. [01:30] - What is Microsoft Graph?[01:56] - How does security work with the Graph SDK?[07:12] - Authenticating a Microsoft Graph client (Demo)[13:50] - Authenticating a Microsoft Graph in ASP.NET (Demo)[21:30] - What are the different flavors of Graph NuGet packages? Useful LinksMicrosoft Graph DocsMicrosoft Graph Dev CenterMicrosoft Graph ExplorerMicrosoft Graph on GitHub

Service discovery essentially is trying to find an answer to the question of what services are available and how do I get to them. In this episode, we chat with Tim Hess and David Dieruf from the Steeltoe team to learn how to setup Service discovery in an ASP.NET Core application with just a few lines of code. [02:40] - What is Service Discovery?[04:08] - Comparing Service Discovery and DNS[06:10] - Setting up service discovery with Steeltoe[13:28] - Configuring the discovery client[21:10] - Inspecting services in Eureka[23:03] - Benefits of Service Discovery[26:52] - Getting start resources Useful Links Steeltoe HomepageService Discovery with Steeltoe.NET Microservices with SteeltoeSteeltoe on GitHub

With Schema stitching, developers can create a unified GraphQL schema from multiple underlying GraphQL APIs. This gives us the benefit of reducing multiple data queries for our data in a single request from one schema. In this episode, Jeremy chats with the author of Hot Chocolate, Michael Staib, about how .NET developers can implement GraphQL schema stitching with Hot Chocolate. [01:57] - What is schema stitching about?[06:00] - Schema stitching with Hot Chocolate[09:08] - Querying with Banana Cake Pop[10:16] - Setting up the GraphQL Gateway[13:56] - Customizing the schema[20:42] - Merging related schemas Useful Links Schema Stitching ExamplesGetting started with GraphQL and HotChocolateCreate web APIs with ASP.NET Core

GraphQL supports the ability to subscribe to event streams to enable somewhat real-time scenarios for both clients and servers. In this episode of the On .NET show, HotChocolate author Michael Staib returns to show us how to enable real-time data fetching with GraphQL using subscriptions . [02:02] - What is real-time data fetching?[04:30] - What are subscriptions used for?[05:48] - Setting up a GraphQL client in Blazor (Demo)[10:55] - Updating the GraphQL schema with fragments[16:38] - Updating the Razor components[24:48] - Using GraphQL variables[28:18] - Adding subscriptions Useful Links HotChocolate in GitHubSubscriptions in GraphQL specIntroductions to ASP.NET core

Hot Chocolate is a GraphQL platform for that can help you build a GraphQL layer over your existing and new infrastructure. In this episode, we're joined by the author of Hot Chocolate, Michael Staib, who shows us how we can start creating GraphQL based Web APIs with Hot Chocolate and some other delicious deserts. [01:27] - What is GraphQL?[04:50] - What's the story behind Hot Chocolate?[05:48] - How does GraphQL compare to RESTful APIs?[06:48] - Setting up a HotChocolate in ASP.NET Core (Demo)[09:43] - Querying with Banana Cake Pop (Demo)[12:00] - Querying relationships (Demo)[21:03] - Where to learn more? Useful Links Hot Chocolate on GitHubGraphQL WorkshopWhat is up with 11 of Hot Chocolate?Create web APIs with ASP.NET Core

KEDA is an open source project and enables event-driven autoscaling for Kubernetes workloads.KEDA scalers can detect if a deployment should be activated or deactivated, and feed custom metrics for a specific event source. In this episode, our friend Jeff Hollan joins Cecil to show us how we can use KEDA to scale out our .NET applications running on Kubernetes [01:15] - What is KEDA?[03:38] - KEDA's relationship with Azure Functions[05:53] - Moving KEDA to the CNCF[08:40] - .NET Worker service demo[12:44] - Supported Keda triggers[14:37] - Working with ACI and Virtual Kubelets[17:09] - Does KEDA work alongside other Kubernetes projects?[18:45] - Getting started with KEDA Useful Links KEDAKEDA on GitHubCreate a function on Linux using a custom container.NET Sample with Service Bus

Progressive Web Applications (PWA) use modern browser APIs and capabilities to behave like a desktop app. Since Blazor WebAssembly is a standards-based client-side web app platform, developers have the ability to leverage these browser APIs and create PWAs using .NET. In this episode, Jeremy is joined by Dan Roth to discuss the built in support for building PWAs with Blazor and show us a few demos of how get started. [01:44] - What are Progressive Web Apps?[02:48] - Getting prepared to make your app installable[05:05] - (Demo) Creating a PWA with Blazor[07:38] - Exploring the manifest and service worker[09:30] - Supporting office scenarios[14:00] - Synchronizing offline updates[19:22] - Push notifications with PWAs[24:46] - (Demo) Setting up notifications in code Useful Links Get started with BlazorBuild Progressive Web Applications with ASP.NET Core Blazor WebAssemblyCall JavaScript functions from .NET methods in ASP.NET Core Blazor

Reverse proxies can help simplify how clients access your backend services. YARP (Yet Another Reverse Proxy) is designed as a library that provides the core proxy functionality which you can customize to fit your application's specific needs. In this episode, Jeremy chats with Chris Ross and Sam Spencer about why they decided to start working on YARP. They show us some demos of various YARP features like live reloading, authorization policies and more. [01:13] - What is the goal of YARP?[02:04] - What's the difference between a load balance vs reverse proxy?[05:04] - Setting up YARP in an ASP.NET Core application[06:39] - Reviewing the route configuration[11:25] - Supporting TLS termination[13:23] - Live reload for configuration[14:33] - Dynamically updating configuration[17:04] - Service Mesh?[18:58] - Using ASP.NET Core authorization policies[20:31] - Getting started with Yarp Useful Links Getting started with YarpYarp on GithubASP.NETCore Middleware

Dapr is a portable, event-driven runtime that makes it easy for developers to build resilient microservice applications that run on the cloud and edge. In this episode, Aman Bhardwaj joins Cecil to talk about the what DAPR types of problems Dapr is trying to solve for developers building microservices. We also get some demos of how to use the .NET SDK for Dapr. [00:55] - What is Dapr?[06:35] - How big is Dapr?[09:00] - The .NET SDK for Dapr[10:50] - Darp's Actor runtime[17:12] - Demo of Dapr Actors [23:20] - Dapr's .NET Client with GRPC[26:08] - ASP.NET Core Integration[31:45] - Dapr's Open Source community Useful LinksDaprDapr blogDapr on GitHubAdding a Little DAPR to Your .NET Microservices