It’s been almost a month, so I guess it’s time for another rave against VSTS.
Currently where I live there are rolling power cuts due to worker strikes. This means that we’re left without power for about 2 hours every day.
That is not much of a problem. The Mac’s battery easily bridges the gap and I can go without internet for a couple of hours.
What really kills me is what happens to Visual Studio when the power cut finds it connected to TFS: a complete block out for several minutes and several “I am competely helpless and you can’t do anythng about it” modal dialogs.
Things go so wrong, that after wading through most of the dialogs the state of the files on the disk is…unknown. Some of the files are read-only (if you were unlucky enough to be in the middle of adding files to the repository), others are not bound to source control and after forcing VS to keep working it at one point gives up the ghost and says goodbye while asking you to report it’s sins to mama MS.
After battling for two days with SQL Server and now this, I’ve just about had enough – got to do some Ruby to keep sane.
The crash is reproducible. A WebService test fails with an exception. On the test result page there is a link to copy the error message. Click on it and VS crashes. Now I don’t know if it’s the specific test with the specific error in combination with the connectivity loss, but I’m not feeling inclined to try and find out at the moment…maybe when I calm down.