Support Visual Studio 2017

It’s pretty simple, see: https://github.com/conan-io/conan/pull/777

Also just a suggestion but VS2017 might make a good topic for a blog post due to it’s new CMake integration, which appears to be incompatible with Conan on first glance but can be tweaked to work with it.

VS2017 supports using CMake directly (as in you can just open a folder with a CMake file and it figures everything out without having to create a solution file). The problem is VS generates the build directory in some unique directory that cannot be predicted. That can be resolved easily by opening up the file CMakeSettings.json (created by Visual Studio when it first tries to open the folder) and changing the ‘buildRoot’ property to the path to any build directories you’d typically create manually (where you’d be able to run conan install).

[NokiDev]

Hi @ForNeVeR I took a first look of your Vs-extension earlier this afternoon, it seems really nice. I haven’t understood some of your UI/label choices. I’ll be happy to talk about it, but isn’t the place to.

Based on what I saw it won’t be a big problem to integrate with CMake based project since logically conan is build system agnostic. In fact it should work with both, at the first layer of implementation and then be specialized with custom features. I’ll probably make a PR this Week end if I have some free time

[ForNeVeR]

@NokiDev FYI: I am one of conan-vs-extension authors (it’s a draft of Visual Studio plugin that helps to work with Conan), and it already does somewhat what you describe: calls conan install for each project configuration (check out the docs and ask me any questions if you want), and also adds a small level of integration to project files.

Unfortunately, currently it works only for vcxproj-based projects, but we definitely want to support CMake-based integration, too (and maybe it’ll be easy to add).