mirror of https://github.com/microsoft/semantic-kernel.git synced 2026-10-12 02:19:06 +00:00

Files

T

Mark Wallace 20b503293c .Net: Update .NET notebooks to use release 1.23.0 (#9311 )

### Motivation and Context

<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

### Description

<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->

### Contribution Checklist

<!-- Before submitting this PR, please make sure: -->

- [ ] The code builds clean without any errors or warnings
- [ ] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [ ] All unit tests pass, and I have added new tests where possible
- [ ] I didn't break anyone 😄

2024-10-17 18:36:20 +00:00

4.5 KiB

Raw Blame History

Basic Loading of the Kernel

The Semantic Kernel SDK can be imported from the following nuget feed:

In [ ]:

#r "nuget: Microsoft.SemanticKernel, 1.23.0"

After adding the nuget package, you can instantiate the kernel:

In [ ]:

using Microsoft.SemanticKernel;
using Microsoft.Extensions.Logging;
using Microsoft.Extensions.Logging.Abstractions;
using Microsoft.Extensions.DependencyInjection;
using Kernel = Microsoft.SemanticKernel.Kernel;

// Inject your logger 
// see Microsoft.Extensions.Logging.ILogger @ https://learn.microsoft.com/dotnet/core/extensions/logging
ILoggerFactory myLoggerFactory = NullLoggerFactory.Instance;

var builder = Kernel.CreateBuilder();
builder.Services.AddSingleton(myLoggerFactory);

var kernel = builder.Build();

When using the kernel for AI requests, the kernel needs some settings like URL and credentials to the AI models.

The SDK currently supports OpenAI, Azure OpenAI and HuggingFace. It's also possible to create your own connector and use AI provider of your choice.

If you need an Azure OpenAI key, go here.

In [ ]:

Kernel.CreateBuilder()
.AddAzureOpenAIChatCompletion(
    "my-finetuned-model",                   // Azure OpenAI *Deployment Name*
    "https://contoso.openai.azure.com/",    // Azure OpenAI *Endpoint*
    "...your Azure OpenAI Key...",          // Azure OpenAI *Key*
    serviceId: "Azure_curie"                // alias used in the prompt templates' config.json
)
.AddOpenAIChatCompletion(
    "gpt-4o-mini",                        // OpenAI Model Name
    "...your OpenAI API Key...",            // OpenAI API key
    "...your OpenAI Org ID...",             // *optional* OpenAI Organization ID
    serviceId: "OpenAI_davinci"             // alias used in the prompt templates' config.json
);

When working with multiple backends and multiple models, the first backend defined is also the "default" used in these scenarios:

a prompt configuration doesn't specify which AI backend to use
a prompt configuration requires a backend unknown to the kernel

Great, now that you're familiar with setting up the Semantic Kernel, let's see how we can use it to run prompts.

4.5 KiB Raw Blame History

Basic Loading of the Kernel

4.5 KiB

Raw Blame History