Poll: Compiler version upgrade in 2019

[silent]

Dear customers,

It's been couple of years when we changed our minimal spec for Windows compiler to Visual Studio 2013. Right now we are thinking about moving to the next versions and we would like to know your opinion on that and your plans for compiler upgrades in your projects for the next year.

Please, mark your answer in a poll that attached to this thread.

Linux compiler upgrade is also considered as an option (especially if we would use some new C++ 11/14/17 features).

 

Previous results: https://developer.unigine.com/forum/topic/4580-poll-compiler-version-upgrade-in-2018/

Thanks!

[Lales.Charles]

Hi,

Yep, VS 2017 or VS 2019 would be soon more than welcome for our internal dev / corporate IT.

Kind regards,
Charles

[paul.abrams]

The guy who manages magnum mentioned it being a nightmare to support vs 2015, 2017 and 2019 altogether.  I'm not sure how difficult it'd be to get vs 2019 support with c++ 17 but that'd be very welcome.  Especially considering https://github.com/skypjack/entt requires the standard.  I wish more libs would support C++ 11 considering a lot of rendering frameworks don't go much further than that.

Edited April 21, 2020 by paul.abrams

[rohit.gonsalves]

I have shifted my development to VS 2019. 

Rohit

[jamie.shelley]

I ran an update to 142 against latest win10 sdk (2.11) and no issues found thus far.
I even have a plugin I have created running an init in there without issues, which was surprising. 
That being said, I imagine you would gain some efficiencies in using some 142 methods, but I don't know about similarly versioned Linux. 

[samthesuperhero]

Did upgrade in VS 2019, as it offered, all worked OK, VS just created the *.sln file, and looks at least at the moment no issues working with Unigine projects in VS 2019