Toolkit Pro - Cannot build 18.0.1 with VS 2017

Print Page | Close Window

Cannot build 18.0.1 with VS 2017

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=23413
Printed Date: 23 December 2024 at 6:54am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Cannot build 18.0.1 with VS 2017

Posted By: MichaelN
Subject: Cannot build 18.0.1 with VS 2017
Date Posted: 10 August 2017 at 3:21pm

The build immediately terminates with the message below. As per the suggested remedy, in VS 2017, THERE IS NO "Tools/Add-in Manager"

StdAfx.cpp

C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.0.1\Source\Common/XTPDLLExports.h(71): fatal error C1083: Cannot open include file: 'afxwin.h': No such file or directory [C:\PROGRA~2\CODEJO~1\MFC\XTREME~1.1\WORKSP~1\TOOLKI~1\TOOLKI~3.VCX]

----------------------------------------------------------------------------

IMPORTANT: If your Visual Studio environment crashed during the build, try

disabling all of your addins and try again. To disable addins:

1. Start Visual Studio

2. Go to Tools/Add-in Manager

3. Uncheck all the checkboxes in the Startup column

----------------------------------------------------------------------------

Replies:

Posted By: g_j_a_i_n
Date Posted: 01 September 2017 at 7:48am

I am getting similar error when building 18.0.1 for VS 2017:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\atlmfc\include\afx.h(62): fatal error C1083: Cannot open include file: 'new.h': No such file or directory [C:\PROGRA~2\CODEJO~1\MFC\XTREME~1.1\WORKSP~1\TOOLKI~1\TOOLKI~3.VCX]

Someone please help.

Thanks.

Posted By: olebed
Date Posted: 03 September 2017 at 1:22pm

Hello,

Have you tried to compile library without DeployWizard ?
Open project and choose necessary configuration.
c:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.0.1\Workspace\ToolkitPro\ToolkitProShared_vc140.vcxproj

I see the same unanswered questions for VS2015.

Regards,
Oleksandr Lebed

Posted By: g_j_a_i_n
Date Posted: 07 September 2017 at 6:06am

I uninstalled Visual Studio 2017, reinstalled and then it worked.

Thanks.

Posted By: xang
Date Posted: 14 September 2017 at 11:21am

Build from Solution gaves:

1>StdAfx.cpp
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.11.25503\atlmfc\include\afx.h(62): fatal error C1083: Cannot open include file: 'new.h': No such file or directory
1>Done building project "ToolkitProShared_vc150.vcxproj" -- FAILED.
2>StdAfx.cpp
2>c:\program files (x86)\microsoft visual studio\2017\enterprise\vc\tools\msvc\14.11.25503\atlmfc\include\afx.h(62): fatal error C1083: Cannot open include file: 'new.h': No such file or directory
2>Done building project "ToolkitProStatic_vc150.vcxproj" -- FAILED.

-------------
Product: Xtreme Toolkit Pro (MFC) version 18.0.1 (with 1-year maintenance)
Platform: Windows 10 RS2 (x64)
Language: Visual C++

Posted By: Jan Oudkerk
Date Posted: 21 September 2017 at 10:47am

Your suggestion to compile the library without the DeployWizard was very helpful for me. I didn’t know about this possibility.

We installed a new PC with Windows 10 and Visual Studio 2017. The Codejock DeployWizard responded very short after startup with an error messagebox telling us “An error occurred during the build process. The Deployment wizard is unable to continue”. Not very informative, so it was hard to find a way to get this working.

Opening the vcxproj file in VS2017 to compile the project made immediately clear what the problem was: Codejock relies on Windows SDK v8.1, which was not installed!

We changed this to Windows SDK V10 and now it works.

Thanks!

Posted By: olebed
Date Posted: 21 September 2017 at 5:51pm

Hello Jan Oudkerk,

Unfortunately Codejock can't release new versions often, but you can find on this forum latest hot fixes from admins or customers, introduce them into code and rebuild library. You can even find bugs or make some improvements in library and post here.

Regards,

Oleksandr Lebed

Posted By: Marco1
Date Posted: 22 September 2017 at 6:46am

olebed wrote:

Sorry Oleksandr, but this is a really bad policy. As a paying customer I expect that minor updates and especially bug fixes are released in a frequent way.
I have no time to read all forum posts just to copy and apply all patches on my own - and I often read "we have already fixed this" by you. Yeah, fine. When you fixed it, pls just release a 18.0.x + 1 version.

This would be extremely helpful and a lot of developers here would greatly appreciate that, I guess.

-------------
Product: XTP 18.3.0 on VS 2017
Platform: VS 2017 / Windows 10 (64bit)

Posted By: olebed
Date Posted: 22 September 2017 at 6:54am

Hello Marco1,

I read such requests from customers all time. I have offered to made separate branch where we can accumulate little or critical fixes. Such changes don't need very big testing and can be released often. But unfortunately for some reason Codejock company can't do this.

Regards,
Oleksandr Lebed

Posted By: olebed
Date Posted: 30 October 2017 at 10:23am

g_j_a_i_n wrote:

I am getting similar error when building 18.0.1 for VS 2017:

Hello,

Try to changing the SDK to version 10 and higher. Some customers use v10.0.15063.0.

Regards,
Oleksandr Lebed