19 June 2017
We have all been there, a customer calls in a bug on the production environment. The first thing we do is that we go to the log files and see if we can find the error. Sadly the developer who wrote the code did not think that anything could go wrong so, so he decided not to spend the time creating a meaningful error message, after all, what could possibly go wrong?... So we end up with a generic error message which does not show the root course of the error. Luckily at Microsoft Build 2017, Microsoft introduced the Visual Studio snapshot debugger.
Page 1 of 1