VS CODE AND .NET ARE QUIETLY TURNING INTO YOUR AGENT CONTROL PLANE
Microsoft is wiring VS Code and .NET into a practical agent platform, with skills, orchestration, and a path to production. The .NET team published reusable ag...
Microsoft is wiring VS Code and .NET into a practical agent platform, with skills, orchestration, and a path to production.
The .NET team published reusable agent skills in dotnet/skills built on the Agent Skills spec, already supported by GitHub Copilot CLI, VS Code, and Claude Code. They also ship a validator to measure if a skill actually improves outcomes, encouraging testable agent baselines instead of ad‑hoc prompts.
A real app walkthrough shows how Microsoft Agent Framework, Foundry, MCP, and Aspire fit together for multi‑agent orchestration, governance, and cost routing. Pair that with the VS Code AI Toolkit’s end‑to‑end build flow in this Agent Builder session, and you have a credible dev-to-prod track. One open question is agent discovery and exposure; a proposed approach for “unlisted numbers” via SARL highlights the need to control who can even find internal agents background.
Agent work is moving from novelty to repeatable engineering with skills, orchestration, telemetry, and governance.
Treating agent discovery as an attack surface avoids exposing sensitive internal capabilities through casual enumeration.
-
terminal
Run a small pilot using dotnet/skills and its validator to measure win rate versus your current prompts on two tasks.
-
terminal
Deploy the Agent Framework sample pattern with Aspire locally, then route through Foundry to compare tracing, cost, and latency.
Legacy codebase integration strategies...
- 01.
Standardize agent calls behind shared skills to reduce prompt drift across repos and services.
- 02.
Hide internal agents behind private endpoints and controlled discovery; treat Agent Cards like secrets with allowlists.
Fresh architecture paradigms...
- 01.
Start with Agent Framework plus Aspire for multi‑agent backends and Foundry for model routing and governance.
- 02.
Prefer MCP for tool integrations to avoid bespoke adapters and simplify maintenance.