Visual Studio 2013 was released a few days ago and with it, updated Express editions for hobbyists and those who don’t require the full spectrum of features the commercial product provides. Unfortunately, VS Express 2013 for Windows Desktop shares a problem with its 2012 predecessor — the removal of the Exception Assistant.
You may remember this issue as something I covered earlier in the year. Despite all the improvements and added functionality, the lack of the Exception Assistant, which allows you to easily continue or make changes to code after an exception occurs, weighed heavily on my productivity, so much so I went back to 2010.
Yesterday I downloaded Visual Studio Express 2013 for Windows Desktop and hit the same issue. There is a workaround, but it’ll kill your productivity even more than doing without the Assistant: placing a
try/catch block around code you think might cause an exception, and then place a breakpoint on the
If only we could always predict what code will throw an exception.
It’s an odd move on Microsoft’s part to persist with this, as it’s not enough to get you to buy Visual Studio, but annoying enough to keep you from using the latest Express editions. I’m not entirely sure who wins in this scenario.
I’ve Given Up On Visual Studio Express 2012. Here’s Why [Lifehacker Australia]