Wednesday, December 17, 2014

Dude, Where's my Include Path in Visual Studio 2013?

I used to really like Visual Studio, but that was years ago. I think it's a rule of nature though that nerds need something to do - and deprived of anything useful we just destroy whatever is around us to have an excuse to make something else.

Visual Studio 2013 looks like it's in the last stages of this sort of decay based on my experience so far. Everything used to be really fast back in the day.  There was a command line build exporter that worked.  Basic stuff like include paths used to be under Project -> Settings. Everything in 2013 needs a dozen clicks through menus named by folks who obviously don't understand what the menus actually do.  Even include paths now has a context menu for some reason.

 I spent way too long messing around with the Configuration Manager, which doesn't do anything useful as far as I can tell, and hit this finally. Open the property pages for the project and go to Configuration Properties -> VC++ Directories. It's not a VC++ directory, but there it is. Add a new line to the "Include Directories" and you are set.  For that target.  Keep doing it over and over until everything is updated.

Here's my project with Qt added in:




I can't see how anyone is supposed to set up a consistent build environment with things like this - this seems to imply that everyone working on anything Visual Studio has to have the exact same system set up or just spends all day updating things.  I have no idea how this would translate into an automated build system without way too much work.

Really this looks like a good way to have large teams of people spending all day clicking on things like crazed chimps looking for food pellets rather than working.


No comments:

Post a Comment