|
You are here |
www.hanselman.com | ||
| | | | |
www.jimmybogard.com
|
|
| | | | | Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the previous post, we looked at techniques for determining the size and scope of our .NET migration effort, as well | |
| | | | |
jamiemaguire.net
|
|
| | | | | In the previous blog post, we saw how to use logging to examine planners and help debug your Semantic Kernel solution. In this blog post, you will see how to expose the customer service agent we've been building in a custom webchat experience using ASP.NET Core. This blog ties together many of the concepts from earlier posts and demos. All previous posts in the series can be found here: First Look, Integrating Semantic Kernel with Open AI (Part 0) - An introduction to Semantic Kernel, who is it for, why ... | |
| | | | |
dylanbeattie.net
|
|
| | | | | Using ASP.NET Core and Azure OpenID Connect to restrict access to admin features based on an authenticated user's email domain. | |
| | | | |
www.frankysnotes.com
|
|
| | | |||