Uploaded September 2026 | Updated November 2026, 2 hours ago
How does the Visual Studio team decide when it’s time to retire a feature?
In this segment from The Future of Visual Studio: Interactive Expert Panel, the team discusses the challenge of modernizing a product with decades of history while continuing to support developers and enterprises that still depend on older workflows, extensions, and technologies.
The conversation covers how usage and telemetry help inform deprecation decisions, why backward compatibility remains important, how Visual Studio is becoming more componentized, and when older capabilities might be removed, turned off by default, or potentially moved to open source.
👤 Panel: Andy Sterland + Anson Horton | Moderator: Mads Kristensen
🔗 Links
• Explore more VS Live! MSHQ sessions: https://aka.ms/vslivehq26
• Join upcoming VS Live! events: https://aka.ms/VSLiveEvents
#vslive #visualstudio
How does the Visual Studio team decide when it’s time to retire a feature?
In this segment from The Future of Visual Studio: Interactive Expert Panel, the team discusses the challenge of modernizing a product with decades of history while continuing to support developers and enterprises that still depend on older workflows, extensions, and technologies.
The conversation covers how usage and telemetry help inform deprecation decisions, why backward compatibility remains important, how Visual Studio is becoming more componentized, and when older capabilities might be removed, turned off by default, or potentially moved to open source.
👤 Panel: Andy Sterland + Anson Horton | Moderator: Mads Kristensen
🔗 Links
• Explore more VS Live! MSHQ sessions: https://aka.ms/vslivehq26
• Join upcoming VS Live! events: https://aka.ms/VSLiveEvents
#vslive #visualstudio








