Intelligent technical talk about .NET, with no ads, for 15 years. Now on YouTube

James is welcomed back to Yet Another Podcast, this time to talk about Vibe Coding with Microsoft’s AI tools.

Video

https://developer.microsoft.com/blog/complete-beginners-guide-to-vibe-coding-an-app-in-5-minutes

https://jamesmontemagno.github.io/podstats

https://www.vscodepodcast.com

https://www.vscodepodcast.com/6

Lance takes us through what MCP is, why it is important, and how to work with it.

Video

You can reach Lance here:
https://bsky.app/profile/lance.boston
https://twitter.com/l_anceM
Https://dvlup.com

Visual Studio 2026 is here. Mads takes us through the highlights

View this podcast on YouTube

Conversation with Scott Hunter (VP Microsoft) about Visual Studio, CoPilot Agents, MCP, Azure, Azure Functions and much more.

Watch on YouTube

Note: ZenCastr ate Scott’s links, but you can get started at https://learn.microsoft.com

Mads K of Microsoft talks about the targeting of Visual Studio and VSCode. Towards the end, I ask him about a few of his favorite plugins.

View this podcast on YouTube

Jeff Fritz (Microsoft) joins me to talk about .NET Aspire, CoPilot Agents and Vibe programming. This is a show not to miss; his enthusiasm is catching and his knowledge is astonishing.

Forage is an AI email assistant that sorts your mail into categories, provides a summary once or twice a day (your choice) and summarizes newsletters into bullet points.

I talk with Richie Bonilla (CEO and co-founder)* about his startup, what lead him to create Forage and how it works.

https://foragemail.com

* Co-founder? Co-Founder? Cofounder?

Prepare to have your mind blown. Copilot Agents are powerful AI tools for Visual Studio Code and Visual Studio. Used to CoPilot? — you ain’t seen nothing yet!

James Montemagno and Burke Holland of Microsoft discuss how to get it, and how to use it.

https://code.visualstudio.com

GitHub Copilot for Skeptics Who Still Think AI is Overrated | BRK124

https://youtube.com/@code

(30+) Visual Studio Code (@vscode.dev) — Bluesky

OpenAPI is the framework of choice for documenting APIs

OpenAPI support in ASP.NET Core API apps
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/openapi/overview?view=aspnetcore-9.0
 
Generate OpenAPI documents at build-time
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/openapi/aspnetcore-openapi?view=aspnetcore-9.0&tabs=visual-studio%2Cvisual-studio-code#generate-openapi-documents-at-build-time
 
The project file property to set the directory where the OpenAPI should be saved is “OpenApiDocumentsDirectory” and it is documented here:
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/openapi/aspnetcore-openapi?view=aspnetcore-9.0&tabs=visual-studio%2Cvisual-studio-code#modifying-the-output-directory-of-the-generated-open-api-file
 
This section contains a summary of how C# types and attributes map to OpenAPI schemas.
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/openapi/include-metadata?view=aspnetcore-9.0&tabs=minimal-apis#include-openapi-metadata-for-data-types
 
We talked about the OpenAPI specification — the latest version is here:
https://spec.openapis.org/oas/v3.1.1.html
 
I also briefly touched on the Overlay specification — that is here:
https://spec.openapis.org/overlay/v1.0.0.html
 
and the Arazzo Specification — that is here:
https://spec.openapis.org/arazzo/v1.0.1.html
 
The Roadmap for ASP.NET Core features in .NET 10 is here:
https://github.com/dotnet/aspnetcore/issues/59443