The .Net samples doesn't work - Corporate proxy and custom SSL chain

Open
#82 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, csharp
Domain
backend, cloud

Research direction

Start with samples/dotnet/00-Getting-Started/README.md and samples/dotnet/00-Getting-Started/Program.cs, especially the AddAzureOpenAIChatCompletion call at line 40. Compare the documented secret names and setup with the sample's expected method usage, then verify that the sample builds and runs for Azure OpenAI; separately determine whether the corporate proxy and custom SSL chain need documented setup.

Written by the indexing model from the issue text.

Description

Hi there,
I've tested some samples under https://github.com/MicrosoftDocs/semantic-kernel-docs/blob/main/samples/dotnet/00-Getting-Started/README.md

And it doesn't work.
I am behind a corporate proxy with a custom SSL certificate chain. This could lead to some problem and would be great to know how to make the sample working in such case.

However the problem seems to be another. As written, I have loaded the variable in secret manager. I am using AzureOpenAI therefore I ran dotnet user-secrets set "AzureOpenAI:ChatCompletionDeploymentName" kind of commands.

And uncommented the line builder.Services.AddAzureOpenAIChatCompletion();.

When I try to build and run it I get error:

Severity	Code	Description	Project	File	Line	Suppression State
Error	CS1501	No overload for method 'AddAzureOpenAIChatCompletion' takes 0 arguments	00-Getting-Started	C:\Users\Source\Repos\semantic-kernel-docs\samples\dotnet\00-Getting-Started\Program.cs	40	Active
Dominant language
Mermaid
Stars
263
Forks
167
Avg merge
3h 2m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftDocs/semantic-kernel-docs

All issues in MicrosoftDocs/semantic-kernel-docs

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.