Toolkit Pro - Visual Studio 2017 Support?

Print Page | Close Window

Visual Studio 2017 Support?

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=23285
Printed Date: 05 May 2024 at 1:34am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Visual Studio 2017 Support?

Posted By: Fredrik
Subject: Visual Studio 2017 Support?
Date 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

Replies:

Posted By: calvi
Date 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.

Posted By: adrien
Date Posted: 13 March 2017 at 5:58pm

We've already built 17.2.0 on VS 2017

-------------
http://www.wingate.com - http://www.wingate.com

Posted By: Marcus
Date 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?

Posted By: adrien
Date 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.

-------------
http://www.wingate.com - http://www.wingate.com

Posted By: markr
Date 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.