mirror of https://github.com/microsoft/agent-framework.git synced 2026-06-16 21:04:09 +08:00

Files

T

westey a3a9147e61 .NET: [BREAKING] Rename AgentThread to AgentSession (#3430 )

* Rename AgentThread to AgentSession

* Add more renames

* Update readme files

* Revert nullable variable change and further fixes.

* Revert change in header name

* Fix some comments and tests

* Update changelog.

* Address PR feedback.

* Fixing code review comments.

* Fix new errors after merging latest code.

a3a9147e61 · 2026-01-26 16:30:25 +00:00

History

Agent_With_AzureAIProject.csproj

.NET: Upgrade to .NET 10 (#2128 )

2025-11-22 04:14:15 +00:00

Program.cs

.NET: [BREAKING] Rename AgentThread to AgentSession (#3430 )

2026-01-26 16:30:25 +00:00

README.md

.NET: Foundry V2 - Update Sample and Docs for clear distinction between Classic/New Foundry Agents. (#2459 )

2025-11-26 14:37:03 +00:00

README.md

New Foundry Agents

This sample demonstrates how to create an agent using the new Foundry Agents experience.

Classic vs New Foundry Agents

Below is a comparison between the classic and new Foundry Agents approaches:

Migration Guide

Prerequisites

Before you begin, ensure you have the following prerequisites:

.NET 10 SDK or later
Azure Foundry service endpoint and deployment configured
Azure CLI installed and authenticated (for Azure credential authentication)

Note: This demo uses Azure CLI credentials for authentication. Make sure you're logged in with az login and have access to the Azure Foundry resource. For more information, see the Azure CLI documentation.

Set the following environment variables:

$env:AZURE_FOUNDRY_PROJECT_ENDPOINT="https://your-foundry-service.services.ai.azure.com/api/projects/your-foundry-project" # Replace with your Azure Foundry resource endpoint
$env:AZURE_FOUNDRY_PROJECT_DEPLOYMENT_NAME="gpt-4o-mini"  # Optional, defaults to gpt-4o-mini