Codejock Forums Homepage
Forum Home Forum Home > Codejock Products > Visual C++ MFC > Toolkit Pro
  New Posts New Posts RSS Feed - Building ToolkitPro v20.2 in Visual Studio 2022
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Building ToolkitPro v20.2 in Visual Studio 2022

 Post Reply Post Reply
astoyan View Drop Down
Admin Group
Admin Group

Joined: 24 August 2013
Status: Offline
Points: 254
Post Options Post Options   Thanks (1) Thanks(1)   Quote astoyan Quote  Post ReplyReply Direct Link To This Post Topic: Building ToolkitPro v20.2 in Visual Studio 2022
    Posted: 08 February 2022 at 7:48am
Official Visual Studio 2022 support has not been added yet indeed, it'll be available only in ToolkitPro v20.3, i.e. the next update.

Though Deploy Wizard doesn't have it, it doesn't mean the code cannot be compiled in Visual Studio 2022, it is actually perfectly compatible in ToolkitPro v20.2 already. It only requires tweaking ToolkitPro project files in order to be able to build it in Visual Studio 2022.
Here are simple steps to achieve it:

1. Make a backup copy of C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v20.2.0\Workspace\ToolkitPro

2. Assuming you have installed projects for Visual Studio 2019, open ToolkitProShared_vc160.vcxproj and ToolkitProStatic_vc160.vcxproj in Notepad or any other plain text editor and replace all occurrences of 'v142' with 'v143' and save the changes as ToolkitProShared_vc170.vcxproj and ToolkitProStatic_vc170.vcxproj respectively.

3. Open ToolkitPro_vc160.sln in a plaint text editor and replace all occurrences of vc160 with vc170 and save the file as Open ToolkitPro_vc170.sln

3. Open ToolkitPro_vc170.sln in Visual Studio 2022

4. For each project and required configuration set Advanced -> MSVC Toolset Version to 14.30.XXXXX value that is available in the dropdown list

5. Save changes and build the needed ToolkitPro configurations using Build -> Batch Build menu option

If it builds without any errors then you have your libraries ready to be used with Visual Studio 2022 project. Please note that the compiled libraries will still have vc160 in their names instead of vc170. It won't cause any linking issue as autolinking in v20.2 will still use vc160 suffix for all libraries.
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.063 seconds.