3 ms·

I agree that the GP wasn't .. coherent. But I don't understand your comment. msbuild resides in (for example) C:\Windows\Microsoft.NET\Framework64\v4.0.30319 W

• johncolanduoni 11y ago
  That version of msbuild isn't fully compatible with the one that lives in VS's folder, even when VS is installed. I've had it fail when trying to use it to compile stock projects made by Visual Studio, without anything fancy in the scripts.
• jheriko 11y ago
  re coherence there is missing context. have you ever tried to build webrtc, for example? (its the worst case i've hit tbh, not all of google's stuff is /that/ bad) its a nightmare. some of the dependencies are utterly horrible (systemd!!!!, old deprecated MS headers from VC6) it seems to be custom scripts called from one build system that trigger another... its below the par of what i would expect from an absolute novice. i hear that internally its a lot easier, because there is infrastructure that downloads all these things and sorts it out for you... but from the outside world its rubbish. i'd rather have a hand crafted visual studio project, xcode project, makefile where i can do one thing and not have to understand the insides of a 'black box' library to use it for anything at all.