|
Visual Studio 2017 Support? |
Post Reply 
|
| Author | |
Fredrik 
Senior Member 
Joined: 22 June 2005 Status: Offline Points: 226 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Visual Studio 2017 Support?Posted: 07 March 2017 at 4:55pm |
|
Hi,
Visual Studio 2017 has been released, when can we expect a version of Toolkit Pro with support for VS 2017? (I can probably add it myself, but better to get an official release.) Thanks, Fredrik
|
|
|
Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0
|
|
 |
|
|
calvi
Groupie 
Joined: 20 March 2004 Location: United Kingdom Status: Offline Points: 43 |
Post Options
Thanks(0)
Quote Reply
Posted: 08 March 2017 at 7:08am |
|
On past experience, Toolkit Pro support for new releases of Visual Studio is available 6-9 months after the launch date.
|
|
|
|
|
adrien
Senior Member
Joined: 30 April 2007 Location: New Zealand Status: Offline Points: 449 |
Post Options
Thanks(0)
Quote Reply
Posted: 13 March 2017 at 5:58pm |
|
We've already built 17.2.0 on VS 2017
|
|
|
|
|
Marcus
Groupie
Joined: 04 June 2006 Location: Germany Status: Offline Points: 42 |
Post Options
Thanks(0)
Quote Reply
Posted: 15 March 2017 at 1:40pm |
|
If 18 is still out of sight, maybe you could release a version 17.3.1 with VS 2017 support?
|
|
|
|
|
adrien
Senior Member
Joined: 30 April 2007 Location: New Zealand Status: Offline Points: 449 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 March 2017 at 9:27pm |
|
I think the only change we did to get CJ 17.2 (we didn't move to 17.3 yet since we patched 17.2 a few places) was to add support in the main CJ header for the version of the compiler.
I think it took my dev about 5 minutes to figure this out, so maybe easier than you fear.
|
|
|
|
|
markr
Senior Member
Joined: 01 August 2004 Status: Offline Points: 442 |
Post Options
Thanks(0)
Quote Reply
Posted: 23 March 2017 at 2:20pm |
|
I've been looking into doing this as well. I think we can make a single change to "XTToolkitPro.h".
So instead of this: #if _MSC_VER == 1900 #define _XTPLIB_VISUALSTUDIO_VERSION "vc140" #endif We would check as follows: #if _MSC_VER => 1900 #define _XTPLIB_VISUALSTUDIO_VERSION "vc140" #endif I believe this works because VS 2017 C++ compiler retains binary compatibility. Adrien, is this consistent with what you did? - Mark R. |
|
|
|
|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options