Skip to main content

Microsoft.Extensions.AI – Part IX–Semantic kernel integration

Semantic Kernel was the first AI library specifically created to build AI agent and chat experiences in .NET. Later the .NET team started working on Microsoft.Extensions.AI as a common abstraction layer for integrating AI capabilities in your .NET applications. As a consequence, these 2 libraries have some overlap and similar abstractions exist in both libraries.

This post is part of a blog series. Other posts so far:

What now?

The good news is that Microsoft is actively working on aligning both libraries and (re)building Semantic Kernel on top of the same Microsoft.Extensions.AI abstractions. This means that as a general recommendation you should start with the Microsoft.Extensions.AI abstractions and move to Semantic Kernel when you need more high level features.


Combine Semantic Kernel with Microsoft.Extensions.AI

This native support for Microsoft.Extensions.AI types means you can now use Semantic Kernel with the broader Microsoft AI ecosystem more seamlessly, with consistent programming models and easy interoperability between different components.

Let me give an example on how both libraries can be combined…

We start by registering an Microsoft.Extensions.AI.ChatClient inside a Semantic Kernel kernel :

We can later resolve this instance to use it inside our Chat app:

Of course, we can use the ChatClient also indirectly through a ChatCompletionAgent from Semantic Kernel:

This is only the beginning on aligning Semantic Kernel with Microsoft.Extensions.AI.

More information

Semantic Kernel and Microsoft.Extensions.AI: Better Together, Part 1 | Semantic Kernel

Semantic Kernel and Microsoft.Extensions.AI: Better Together, Part 2 | Semantic Kernel

AI and Vector Data Extensions are now Generally Available (GA) - .NET Blog

Vector Data Extensions are now Generally Available (GA) | Semantic Kernel

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more