On Friday, 25 September 2015 at 03:00:12 UTC, Jonathan M Davis
wrote:
I, for one, was very excited when I found out that you could
actually run VS builds from the command line rather than having
to open up VS. And at my last job, I redid our build stuff so
that we used cmake to generate the build stuff for both Linux
and Windows so that we didn't have two build systems to
maintain, and with that, the _only_ reason that I ever had to
open up VS was to debug on Windows. It was great.
Unfortunately, at my current job, we're entirely Windows, so
everything's a huge mess in VS rather than using cmake, and
most of the devs are totally Windows devs, so they'd probably
freak out at the idea that the .vcproj files are generated, and
you don't edit any settings inside of VS. So, there's no way
that I'm going to get the beauty of cmake again here. I'm
forced to open up VS more - and we're using the muck that is
TFS, which pretty much requires opening up VS to manage source
control (though the TFS power tools help).
TFS has a CLI client. Why would you automate builds if you can't
automate getting fresh sources from source control?
