Csharp conversation API quickstarts

[alicejgibbons]

Description

• Csharp conversation API quickstarts
• Rewrote @WhitWaldo's PR: Added Dapr Conversation .NET Quickstart #1133 to keep the simple for quickstarts and then we can move his Anthropic example to Dotnet SDK repo
• Small readme updates to golang

Issue reference

We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #1103 #1105

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• The quickstart code compiles correctly
• You've tested new builds of the quickstart if you changed quickstart code
• You've updated the quickstart's README if necessary
• If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

[alicejgibbons]

@WhitWaldo can you review the Conversation Client instantiation here? Should I do it a different way?

Also, is it weird putting the builder/app in a Class? Can remove that...

[WhitWaldo]

This is precisely right. As this is configured to use a "Microsoft.NET.Sdk.Web" project, this is the appropriate way to set up the "app builder" itself. Dapr then gets registered on line 28, DI finalized on line 29 and the Dapr client instantiated from that DI pipeline on 32.

Technically this could be shortened a little bit as single-file C# apps don't as much of the window dressing any longer, but this is fine - if you want to shorten it, remove lines 19, 20 and 54 (class Program { })

[WhitWaldo]

The rest of it looks great

[WhitWaldo]

Missing a line here: await app.RunAsync(); - while not strictly necessary since we don't need the whole web server in this example, it'd be a good practice to add it.

[alicejgibbons]

Thanks for checking this out! This got merged but will add this feedback into my next PR

[WhitWaldo]

This is precisely right. As this is configured to use a "Microsoft.NET.Sdk.Web" project, this is the appropriate way to set up the "app builder" itself. Dapr then gets registered on line 28, DI finalized on line 29 and the Dapr client instantiated from that DI pipeline on 32.

Technically this could be shortened a little bit as single-file C# apps don't as much of the window dressing any longer, but this is fine - if you want to shorten it, remove lines 19, 20 and 54 (class Program { })

[paulyuk]

LGTM. I like the consistency across the languages and the feature to more dynamically take inputs

[paulyuk]

Thank you to both @WhitWaldo and @alicejgibbons for this great contribution and collab.