Our build machines (hanging off of TeamCity) were failing to run a little MSBuild command for web deploy publishing using a pubxml file. It would "work on my machine" perfectly fine, but the same command in the same environment on the build machine would simply stop after it was built and proudly pronounce "Done!" without actually publishing the files to our web server.
Not only that, but how do you Google something that hasn't failed? Eventually, you can, apparently. I ended up landing on a link that I recognised from the first time I searched for this particular issue, which references this, which then states:
If you specify an individual project instead of a solution, you have to add a parameter that specifies the Visual Studio version.It boils down to adding the following switch explicitly stating what VS version you are using, in my case, 2012:
Makes sense, whatever. But wait! Why on earth does it work on my local machine at the project level without specifying a Visual Studio version? No idea and I haven't got to the bottom of it.
Suffice to say, the fix is going in and I'm moving on with my life.
I hate unexplained problems like these...