Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS 2017 support #289

Closed
kayru opened this issue Mar 7, 2017 · 7 comments
Closed

VS 2017 support #289

kayru opened this issue Mar 7, 2017 · 7 comments

Comments

@kayru
Copy link

kayru commented Mar 7, 2017

It would be great to have VS 2017 IDE project generator and toolchain support.

@deplinenoise
Copy link
Owner

Agree! You volunteering? :)

@kayru
Copy link
Author

kayru commented Mar 8, 2017

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

@kayru
Copy link
Author

kayru commented Sep 10, 2017

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 :)

@deplinenoise
Copy link
Owner

deplinenoise commented Sep 10, 2017 via email

@kayru
Copy link
Author

kayru commented Sep 10, 2017

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.

@leidegre
Copy link
Contributor

leidegre commented Sep 11, 2017

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.

@leidegre
Copy link
Contributor

#292 for further discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants