Microsoft sucks!

This is no revelation. But we M$ products at work, and one which I use quite a bit is Microsoft Visual Studio 2003 and Visual Source Safe. This morning, after compiling an application successfully, Visual Studio went bye-bye silently. No application exception, nothing in the event log. Nada. A reboot didn’t seem to fix the problem. I’ve narrowed down the problem to projects that are checked into Visual Source Safe. I can’t seem to open those projects, but projects that are not checked into revision control are accessible.

And yes, I checked the VSS server and I can get into that just fine.

This sucks becuase I was about to finish something up and get it published and check it off my list and move on to the next task. Now I’ve got to spend time I don’t have trying to figure out what the heck is going on!


UPDATE: It’s all working now, although it took a threat of setting my computer out to sea and praying for a hurricane to get it to cooperate. Incidentally, after I clicked the “Save Post” button on the initial post (when, in fact, I felt like screaming!), Tears For Fears, “Shout” came onto my iPod:

Shout, shout,
Let it all out.
These are the things
I can do without
Come on; I’m talking to you
Come on.

What a coincidence, eh?

Published by Jamie Todd Rubin

Jamie Todd Rubin writes fiction and nonfiction for a variety of publications including Analog, Clarkesworld, The Daily Beast, 99U, Daily Science Fiction, Lightspeed, InterGalactic Medicine Show, and several anthologies. He was featured in Lifehacker’s How I Work series. He has been blogging since 2005. By day, he manages software projects and occasionally writes code. He lives in Falls Church, Virginia with his wife and three children. Find him on Twitter at @jamietr.