Cannot deploy Toolkit to VS
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=17387
Printed Date: 20 June 2025 at 5:38am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Cannot deploy Toolkit to VS
Posted By: sl@sh
Subject: Cannot deploy Toolkit to VS
Date Posted: 06 October 2010 at 12:05pm
I am currently evaluating the new VS 2010 for our application, but cannot get it to compile because our CodeJock Toolkit Pro version does not support VS 2010.
I downloaded and installed the current trial version of Toolkit Pro, but when I try to deploy the libraries and headers to my VS paths, the deployment wizard will not let me pick any of the VS vresions installed on my system (there are actually 3 now, as the VS 2010 installation also installed VS 2008 - don't ask me why). All the choices on the dialogue are disabled!
I am stuck now! is there a way to manually deploy the libs and includes and how would I go about that? Or what could there be wrong with the deployment wizard, is there any way to fix it?
Does the current version of Toolkit Pro and it's deployment wizard really work with VS 2010, i. e. does it correctly deploy to the VS 2010 paths for other people?
|
Replies:
Posted By: sl@sh
Date Posted: 07 October 2010 at 5:19am
Could halfway resolve it now by myself. I had to remove the CodeJock software and then reinstall it after rebooting the machine. Then at least I got VS 2010 to selct, but still, I could select neither VC9 (2008) nor VC7.1 (2003.NET)!
I am having different issues now (does not link properly), but I will post this in a new and properly named topic if I cannot resolve it by myself...
|
Posted By: Oleg
Date Posted: 08 October 2010 at 7:05am
Yes, in list you see only Visual Studios that currently available in your PC.
-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS
|
Posted By: sl@sh
Date Posted: 08 October 2010 at 7:48am
I am currently working with VS 2003.NET so it is definitely on my PC, and it is not in the list.
That said, while I got XTP to deploy for 2010, the way it is compiled is incompatible with our application. I can not link it. Changing our own project's settings to match the Toolkit's is not an option as this would conflict with other third party libraries. We need to manually rebuild the Toolkit library with the option /Zc:wchar_t- , but we would need the toolkit project files to accomplish that. The trial version does not include these project files however, so we are stuck! The only libraries provided are those with and without using Unicode.
Judging by the product description on the homepage, the current version of the Toolkit does not support VS 2010, and the trial version is in fact some kind of beta version for the next release. This means buying the upgrade now won't help either!
Is it possible to get a trial version for unicode compiled with the option /Zc:wchar_t- ?
|
Posted By: evoX
Date Posted: 17 October 2010 at 1:57pm
the deployment wizard crashes on systems with windows 7 which had previously installed Visual Studio 2008 and then 2010. I had to compile the libraries on a system which did not have VS 2008 installed before.
-------------
Product: Xtreme ToolkitPro 19.30
Platform: Windows 10 64bit
Language: Visual C++ (VS 2019)
|
Posted By: sl@sh
Date Posted: 18 October 2010 at 11:19am
My OS is Windows XP (SP3), not Windows 7. Also I did not have VS 2008 installed before, it only got partly installed by the VS 2010 installation (i. e. just compilers and stuff for the ability to compile under Visual C++9.0 instead of 10.0, but within the VS 2010 IDE).
I also issued a support ticket two weeks ago, but no response yet.
I still need a library that is compiled for VS 2010 with /Zc:wchar_t- ! In 10 days the trial period will run out and I might not be able to actually test anything until then if I cannot get that. All it would take is the project files to let me change the settings and recompile manually, but they are not accessible.
|
|