It isn’t only Windows 10 due for the support axe on October 14. Other Microsoft products will soon be stashed in Redmond’s cupboard of forgotten dreams, including the venerable Visual Studio 2015.
While Visual Studio Code, which tops the charts in the 2025 Stack Overflow developer IDE survey, might garner all the attention, Visual Studio (29 percent of votes) is not far behind in usage; many developers have had a run-in with the bloated beast in their careers.
The number of tools in Visual Studio has exploded over the decades since its debut at the end of the last century.
However, its longevity means that plenty of older versions are still hanging around. Visual Studio 2015 is to be the next in line for the end of security updates from Microsoft.
The suite of development tools was the last to support Windows 8, the last to support targeting Windows XP SP2, and the first to support Windows 10. It arrived shortly before Windows 10 and featured prominently in the company’s dreams for the Universal Windows Platform (UWP), which promised developers the possibility of the same Windows 10 app running on multiple device types.
Alas, things did not quite pan out that way. Firing up Visual Studio 2015 today is a reminder of Microsoft’s grand developer vision that fell apart after only a few years.
Alongside the end of support for all editions of Visual Studio 2015, support will also be ending for associated products, including Visual Studio Team Foundation Server 2015 and the Visual C++ Redistributable for Visual Studio 2015.
There have been three updates since Visual Studio 2015 was released. Two of these, Visual Studio 2017 and 2019, are already in extended support. The latest version, Visual Studio 2022, will remain in mainstream support until January 21, 2027, with extended support going on until January 13, 2032.
Microsoft strongly recommends that users make the leap to Visual Studio 2022, “which brings the power of Copilot to your development workflow.”
Right. We asked Copilot how to make a LightSwitch application work in Visual Studio 2022, and it did the electronic equivalent of laughing in our faces. It’s an extreme example (Visual Studio 2015 was the last version to support that particular Microsoft vision for line-of-business application development), but it serves to highlight the challenges developers might face when migrating from one version of Visual Studio to another as Microsoft moves on to the next Big Thing.
A careful look at Microsoft’s guide on migrating projects to Visual Studio 2022 would therefore be prudent for any developers still on Visual Studio 2015 and considering a move before October 14. ®