Error when upgrading t Toolkit Pro 24.0

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I have a MFC based Windows Application that compiles, builds and runs just fine with VS 2010 and Toolkit Pro 15.3.1. I am evaluating updating to Toolkit Pro 24.0.0 while also moving to VS 2019. I am able to get the code to compile and build just fine. However, I am getting the following error when setting the EnableMarkup() property on a CXTPRibbonBackstageButton object. This works just fine with Toolkit Pro15.3.1.
The error is 

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

Microsoft Visual C++ Runtime Library

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

Debug Assertion Failed!
Program: C:\**********\ToolkitProEval2400vc160D.dll

File: D:\Package\Temp\Eval\ToolkitPro\Source\Common\XTPApplication.cpp

Line: 103
Expression: NULL != m_pComInit
---------------------------
Any idea why this is happening? 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
CJ_NN_05 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 December 2024 Status: Offline Points: 3	Post Options Post Reply Quote CJ_NN_05 Report Post Thanks(0) Quote Reply Topic: Error when upgrading t Toolkit Pro 24.0 Posted: 27 December 2024 at 2:00pm
	I have a MFC based Windows Application that compiles, builds and runs just fine with VS 2010 and Toolkit Pro 15.3.1. I am evaluating updating to Toolkit Pro 24.0.0 while also moving to VS 2019. I am able to get the code to compile and build just fine. However, I am getting the following error when setting the EnableMarkup() property on a CXTPRibbonBackstageButton object. This works just fine with Toolkit Pro15.3.1. The error is --------------------------- Microsoft Visual C++ Runtime Library --------------------------- Debug Assertion Failed! Program: C:\**********\ToolkitProEval2400vc160D.dll File: D:\Package\Temp\Eval\ToolkitPro\Source\Common\XTPApplication.cpp Line: 103 Expression: NULL != m_pComInit --------------------------- Any idea why this is happening?

astoyan Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 24 August 2013 Status: Offline Points: 315	Post Options Post Reply Quote astoyan Report Post Thanks(1) Quote Reply Posted: 29 December 2024 at 1:28pm
	Please make sure that your main application class is derived from CXTPWinApp. Regards, Alexander

CJ_NN_05 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 December 2024 Status: Offline Points: 3	Post Options Post Reply Quote CJ_NN_05 Report Post Thanks(0) Quote Reply Posted: 10 January 2025 at 6:02am
	Alex, Thanks for your prompt response. Sorry, I was out over the New Year's break hence couldn't reply earlier. That did address the original issue. However, I now get a more generic assert at runtime. This is an outcome of the latest change. Any idea what might be going on? --------------------------- Microsoft Visual C++ Runtime Library --------------------------- Debug Assertion Failed! Program: C:\WINDOWS\SYSTEM32\mfc140d.dll File: D:\a\_work\1\s\src\vctools\VC7Libs\Ship\ATLMFC\Src\MFC\oleinit.cpp Line: 49 ---------------------------

mnvew Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 January 2025 Location: Tucson, AZ Status: Offline Points: 4	Post Options Post Reply Quote mnvew Report Post Thanks(0) Quote Reply Posted: 18 January 2025 at 8:13pm
	I ran the 24.0.0 deployment wizard, and it took several minutes to scroll through all the build files, as usual. When finished, the Bin and Lib folders are both empty inside C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v24.0.0 I repeated the deployment 3 times with the same result.

astoyan Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 24 August 2013 Status: Offline Points: 315	Post Options Post Reply Quote astoyan Report Post Thanks(0) Quote Reply Posted: 07 February 2025 at 2:35pm
	The latest Toolkit Pro v24.1 fixes this issue. If you still can reproduce it after upgrade then try to build Toolkit Pro manually in Visual Studio 2022. The solution file can be found in C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v24.1.0\Workspace\ToolkitPro. If you see build errors then report them here or create a support ticket with all related details. Thank you. Regards, Alexander