VS 2017 support about tundra HOT 7 CLOSED

If it's as simple as VS 2015 support, then sure :)

from tundra.

Agree! You volunteering? :)

from tundra.

FYI, I have a super hacky support for vs2017 here: https://github.com/kayru/tundra/commits/vs2017
Though I really have no idea what I'm doing or how to do it properly :)

from tundra.

from tundra.

I only have vs2015 & 2017 installed. They appear to both work. I'll file a PR, but it would be good if someone could test other VS versions.

from tundra.

LGTM

I used to have all versions of VS installed dating back from 2008 and forward but since I no longer have to write software that supports Windows XP I don't.

I think, that the people that need VS2008 support can use an older version of tundra, if we end up breaking something (because I have used them extensively in the past and they have worked well). I only use VS for debugging nowadays. VS Code has by large replaced my editing needs. Not sure how big of a deal the IDE support will be in the future. More and more IDEs are moving to a file system based approach where you don't need to track project files in a separate file. Though I guess this depends on how your environment is set up to include/exclude files through tundra. Just my two cents.

I should add that it's always been possible to use a newer version of Visual Studio but older versions of the compiler, while we were using the VS2008 C++ compiler for XP support we never used anything but the most recent version of the IDE because of language support and what not. The experience was often better on the more recent version of VS. I think, maintaining older tool chain support is more important than generation of IDE project files.

from tundra.

#292 for further discussion

from tundra.