Visual Studio✓

🧠 C++ std::async looks simple… until the standard enters the chat. 😅 Immediate or deferred? Same thread or new thread? And async | deferred? The implementation gets to choose. 🎲 Decode the mental model 👇

🚀 Tab wrangling, now keyboard-first in Visual Studio 2026 v18.11. ⌨️ Ctrl+Shift+PgUp/PgDn → move tabs ⚡ Ctrl+NumPad1–9 → jump by visual position Arrange your working set, then fly between files. 🧑‍💻

No symbols. No source code. Just a crash dump staring back at you. Used to be the end of the story. Marco Peyrot Carrion shows what changed. The whole process:

Buried in chat history. Forgotten by tomorrow. Yeojun Han turns AI prompts into reusable workflows:

🧵 C++ futures, round 2! ⚙️ See how std::promise + std::packaged_task build on shared state, with get_future() providing the IOU while results or exceptions flow back through the source. 🧠 Async C++, demystified. 👇

🧰 AI isn’t replacing the developer toolkit. It’s expanding it. 🤖 At VSLive! San Diego, developers shared how AI + hands-on experimentation are reshaping how they learn and solve problems, while developer judgment stays essential. 🧠⚡ 👉 Read:

Turn your expertise into reusable AI skills. Dalia Abo Sheasha shows how in this clip from #VSLive! MSHQ. Dive into the full session:

GPT-6.1 Terra from OpenAI is now generally available in Visual Studio Copilot. In GitHub's early testing, GPT-6.1 Terra solved noticeably more terminal and C# coding tasks than GPT-5.6 Terra. It works in focused, consolidated steps on well-scoped tasks. Try it out for everyday agentic coding at a lower cost than GPT-6.1 Sol. Learn more: #VisualStudio #GitHubCopilot #AI

🧠 C++ futures, minus the magic. 🪄 std::promise, std::async + std::future boil down to a shared source: store a value/exception, synchronize with mutex + condition variable, then retrieve or consume it. ⚙️🧵 👉 Read:

🛑 Build failed? Then why is the rest of the solution still building? 😅 Visual Studio 2026 18.11 adds an opt-in stop-on-first-project-failure setting. Queued projects don’t start, active builds stop safely, and you can jump back to fixing the real error faster. ⚡🛠️ In test builds: 94% less post-failure waiting. 👀 👉 Read the blog:

Your AI agent can query your database without writing a single line of SQL. 烙 Bob Ward shows how:

You've got one afternoon to level up. Where do you go?

🧠 C++/WinRT access specifiers hit differently. Implemented interface = public 🌎 - public = module-internal 📦 - protected = derived types - private = same class 🔐 The Old New Thing explains why. Read 👇

Semantic search is powerful, but sometimes exact keywords are still the answer. Anna Hoffman tackles why the real answer might be a hybrid of both:

What if you could group unrelated types without an inheritance hierarchy? Dustin Campbell and Mads Torgersen explore C# unions:

One YOLO deploy to prod is all it takes. Drew Skwiers-Koballa has a safer way:

👀 What happens when Security Tool A hooks a system function… then Security Tool B hooks a function Tool A depends on? 💥 Detours meet detours. 🔐 Quarantine meets interference. 🧩 Debugging gets spicy. Read 👉

Code as an asset, not an artifact. AI writes it fast, but future you maintains it. That's exactly what Mads Kristensen gets into:

Give AI tools, not just prompts. Kayla Cinnamon and James Montemagno build a custom tool the model can call instead of guessing. See it in action:

💥 Your CPU just hit code that should never execute. But was it int 3 or ud2? 👀 int 3 → “there’s no code here” ud2 → “you reached an unreachable/undefined path” 😬 Same crashy vibes. Very different debugging clues. 🧠⚙️ 👉

AI found a 90% optimization. It still needed an engineer's judgment call. Mark Downie and Sireesha Pisipati get into it. See how:

Anna Hoffman argues your database belongs in source control, just like your application code:

🤯 How can an undefined CPU opcode… have operands? Welcome to x86 history. 🧠⚙️ 0F FF could be decoded + parse operands before 💥 invalid opcode. Then backward compatibility helped keep PADDQ out of its natural slot. CPU archaeology awaits. 🏺 Read 👉