News

Visual Studio's Next Act: Faster, Smarter, More AI-Driven

With a focus on everything from AI-powered development to .NET MAUI, Microsoft hosted developers from around the world at its Redmond headquarters for the latest edition of the Visual Studio Live! conference. The multi-day event featured deep dives by Microsoft engineers, live commentary from the Visual Studio Toolbox team, and a showcase of what's next for the company's flagship IDE.

"There's something special about hosting developers at Microsoft HQ -- and this year's Visual Studio Live! Redmond reminded me why I love these events," said Microsoft's Jim Harrer in an Aug. 13 blog post about the event. "The energy in every room was electric. From the moment the first session kicked off, developers leaned in, asked smart, challenging questions, and took every opportunity to connect with the Product Managers and engineers from Visual Studio, Azure, and GitHub Copilot."

Taking place Aug. 4-8, the conference offered sessions across Visual Studio, Azure, GitHub Copilot, and .NET, blending in-person interaction with live-streamed coverage for remote viewers. The highlight came during the Tuesday keynote, now available in a video titled The Future of Visual Studio, led by longtime Microsoft program manager Mads Kristensen, who outlined upcoming capabilities designed to make the IDE faster, more flexible, and more deeply integrated with AI.

Mads Kristensen at Visual Studio Live!
[Click on image for larger view.] Mads Kristensen at Visual Studio Live! (source: Microsoft).

Kristensen and colleagues revealed plans for a new major version of Visual Studio, a faster release cadence, expanded AI and Copilot functionality, and user experience enhancements built directly from community feedback. Here's a look at the most significant developments on the horizon.

New Release Cadence
Visual Studio is moving from a 3-4 month release cycle to monthly updates. This faster cadence allows new features, especially AI and Copilot enhancements, to ship as soon as they are ready instead of waiting for major releases.

Next Major Version: "Visual Studio Next"
The 18th major version of Visual Studio is in development, with early testers reporting significant performance improvements and a refreshed design. Key updates include:

  • Performance & Design - Faster load times, smoother operation, and a modernized UI.
  • Backwards-Compatible Extensions - Extensions from the previous major version will work without requiring updates from their authors.
  • Theming Overhaul - Ships with 10 built-in themes, allows independent theming of editor and UI, and makes custom themes easier to create.
  • New Settings System - JSON-backed settings that are searchable, filterable, and can follow specific projects, enabling automatic theme or configuration changes per solution.
  • UI Refinements - Small but impactful changes, such as narrower line number margins for better space usage.

AI and Copilot Integration
AI capabilities are being deeply embedded into Visual Studio to accelerate workflows and give developers more control. Highlights include:

  • Bring Your Own Models - Add API keys for OpenAI, Anthropic, Google, and other providers, with easy selection via the new model picker.
  • Agent Mode - An AI assistant that can plan, execute, and iterate on coding tasks, implement multi-file changes, and interact with connected tools like GitHub, Azure, and Figma.
  • Model Context Protocol (MCP) - Integrates external tools and services securely, with fine-grained permission controls and expanded spec support.
  • Profiler Agent - Runs performance benchmarks, analyzes bottlenecks, proposes optimizations, and applies changes automatically.
  • .NET Upgrade Agent - Guides step-by-step upgrades to newer frameworks, now generally available in Agent Mode.

Expanded AI Use Cases
Copilot and Agent Mode now support a wider range of tasks:

  • Generating specifications from GitHub issues and implementing them according to project standards.
  • Delegating entire tasks or features to specialized agents while retaining the option to review and modify changes in progress.
  • Using a fleet of agents for coding, upgrading, diagnostics, and other specialized workflows, with more planned for future releases.

Commitment to Fundamentals
Alongside new capabilities, Microsoft is maintaining a strong focus on quality-of-life improvements, eliminating "paper cuts," and supporting both cutting-edge technologies and legacy workloads. Over the past year, more than 4,500 user-reported issues have been fixed and 290 feature requests implemented, reflecting an ongoing emphasis on community-driven development.

See Harrer's post linked above for more information about the conference, including especially interesting sessions now available for on-demand replay.

The next VSLive! developer conference is coming to San Diego Sept. 8-12. Learn more here.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Copilot Billing Shock Hits Developers

    Developer complaints about GitHub Copilot's new usage-based billing model have centered on unexpectedly rapid AI credit consumption, and neither GitHub nor Microsoft has responded directly to the backlash, though they have previously published guidance to lessen model usage costs.

  • Hands On with GitHub Copilot App Technical Preview: Turning a Blazor Issue into a PR

    GitHub's brand-new Copilot desktop app, in technical preview, handled a small Blazor issue from planning through pull request creation, but the hands-on test also showed why developers still need to verify agent work in the running app before merging.

  • At Build 2026, Microsoft Sets Up Windows as an OS for AI Agents

    Microsoft's Build 2026 Windows developer announcements point to a broader platform strategy for agentic AI, spanning terminal workflows, local models, app-building skills, Cloud PCs and operating system-level containment.

  • Slammed by Copilot Usage-Based Billing on Day 1, Facing $180 Bill for June

    A journalist using GitHub Copilot Pro details how a broken editorial workflow on day one of usage-based billing led to runaway token consumption, a projected $180 monthly bill, and practical tactics for cutting AI credit burn.

Subscribe on YouTube