My development team is working on a solution with several projects. We share this solution via TFS. Recently one of the developers joined in one development of one of the projects (called "VMC14"). This project works (debugs, runs, etc) on all other developer computers. However when this new developer got the latest source he found he couldn't run it. He could run every other project within the solution, just not this one project. Whenever he tried it would build without error but then die upon running. Sometimes even freezing the VS2012. He upgraded to 2VS2013 (which most of us were using) and had the same issue. We even tried building a release on someone else's computer and running that exe on his. That failed to run as well.
Eventually one of the other programmers found that it was the name of the project that was the problem. He found this out by creating a new empty project on the troublesome system name "VMCTest" and that failed to run as well.
So the question is why would the name of the project be an issue? And why only on this one computer? What setting on his computer would clash with the project name? My guess is that it has to be a setting somewhere because the computer itself is the exact same computer we all have (we all got replacements at the same time last year).
If anyone has any theories, I would love to know. Currently the only workaround we have is to rename the output for the project on his system. Not a workaround that's great.