error evaluating the toolkit

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

   hi
i am trying to evaluate the MFC toolkit.
i downloaded and installed "ToolkitProEval.MFC.v15.1.3"

I've tried to compile one of the samples and got the error:
"the application was unable to start correctly (0xc0150002). click OK to close the application"

i am using windows 7 x64
visual studio 2005 SP1 Team Edition for Software Developers
version: 8.0.50727.867

10x

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
bibi Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 November 2011 Status: Offline Points: 4	Post Options Post Reply Quote bibi Report Post Thanks(0) Quote Reply Topic: error evaluating the toolkit Posted: 02 November 2011 at 1:56pm
	hi i am trying to evaluate the MFC toolkit. i downloaded and installed "ToolkitProEval.MFC.v15.1.3" I've tried to compile one of the samples and got the error: "the application was unable to start correctly (0xc0150002). click OK to close the application" i am using windows 7 x64 visual studio 2005 SP1 Team Edition for Software Developers version: 8.0.50727.867 10x

bibi Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 November 2011 Status: Offline Points: 4	Post Options Post Reply Quote bibi Report Post Thanks(0) Quote Reply Posted: 09 November 2011 at 4:15am
	HI any news regards my problem? i tried to run the binary compiled of one of the samples on another machine (win2003 under vmware) and had the same problem (this machine also have vs2005 sp1 installed) i had another problem: i tried to run the installer on a win2003 server (installed on vmware esx server) the installer crashed when clicking the "install" button in one of the pages of the installer wizard. i used all the default settings in the installer except that i unchecked the vc6 option (as i don't have it)

ABuenger Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 February 2006 Status: Offline Points: 1075	Post Options Post Reply Quote ABuenger Report Post Thanks(0) Quote Reply Posted: 20 November 2011 at 12:02pm
	Hi, seem there is an issue with WinSxS or mixed 32/64-bit DLLs. Did you also install the "Visual Studio 2005 Service Pack 1 Update for Windows Vista"? I suggest to try it on a 32-bit system. Do all samples fail? Maybe one has a wrong manifest, let me know which one fails. In the retail version you wouldn't see such issues as you compile the toolkit and application yourself. Please try the samples from our website. Andre
	Codejock support

bibi Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 November 2011 Status: Offline Points: 4	Post Options Post Reply Quote bibi Report Post Thanks(0) Quote Reply Posted: 24 November 2011 at 4:16am
	Hi Yes i installed "Visual Studio 2005 Service Pack 1 Update for Windows Vista" the still persist. ( i tried running the samples from the commandbars folder) most of the machines in my work place are 64bit win7, i would be hard to find a 32 bit one with VS. the compiled samples 64/32 bit from your site are running. i could not recommend the toolkit to my boss without evaluate it first.

SuperMario Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 14 February 2004 Status: Offline Points: 18057	Post Options Post Reply Quote SuperMario Report Post Thanks(0) Quote Reply Posted: 12 December 2011 at 9:24am
	You have to use the latest SP for vs 2005, we only use the latest versions to build the Dlls. You have an old SP.

grahamf Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 29 October 2009 Location: United States Status: Offline Points: 13	Post Options Post Reply Quote grahamf Report Post Thanks(0) Quote Reply Posted: 12 December 2011 at 10:06am
	I believe bibi is running the latest SP (which is 1) for VS 2005. However, there have been security updates to SP1 which may cause assembly issues with the CRT/MFC. bibi, check the application event log and see if you have missing assemblies for CRT/MFC than what is required. The latest VS 2005 SP1 redistributable package I have (8.0.50727.6195) have the following links: Knowledge Base: http://support.microsoft.com/kb/2538242 Download: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26347 Note: CJ might be using an older security update. You might be able to tell from the event log. Note: Compiled programs will require this update if you are installing them on other machines.

bibi Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 02 November 2011 Status: Offline Points: 4	Post Options Post Reply Quote bibi Report Post Thanks(0) Quote Reply Posted: 13 December 2011 at 8:18am
	this is the error from the event log: Activation context generation failed for "C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v15.1.3 (30 Day Trial)\Bin\vc80\ToolkitProEval1513vc80D.dll". Dependent Assembly Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.6195" could not be found. Please use sxstrace.exe for detailed diagnosis. after running windows update (and updating 2 security updates for VS2005) the crash is gone. however, the evaluation period is over without able to evaluate the product. the sample is still running after the trail end message, but i am not sure if it's still useful for evaluation. if not, what can be done to extend this period. p.s: please update your download area and state that not only the latest SP should be installed but also all the security updates. 10x

SuperMario Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 14 February 2004 Status: Offline Points: 18057	Post Options Post Reply Quote SuperMario Report Post Thanks(0) Quote Reply Posted: 13 December 2011 at 1:04pm
	Nothing can be done to extend it, but 15.2.1 just came out and you can tart a new 30 days with that.