Version 18.0.1 Deploy Wizard

Seriously, Visual C++ 6.0?
I mean, this is nearly 20 years old (lastest updates like 15 years old?) ...
IMHO it's more than normal if this is a little unsupported by now, like W2K.
Just a thought.

Kenneth, you can check  keys in windows register in path

HKEY_CURRENT_USER\Software\Codejock Software\{product name}

{product name} can be "ToolkitPro", "Calendar", "ChartPro" ....
Also HKEY_LOCAL_MACHINE can be used  instead of HKEY_CURRENT_USER.

There are should be defined  key "Installation Directory" with correct path  and "License" with correct license.

May be you run installation or deployment without admin permissions?

Here is an image of the directory where the 18.0.1 files were placed:



Can you please tell me what the deploy wizard is expecting as input?

This does not make any sense. I downloaded the Codejock program "Codejock.ToolkitPro.MFC.18.0.1" and entered the key as requested. As the name reflects, I want ToolkitPro, MFC version 18.0.1, which is all you need to know. Your wizard unpacks and installs all the required files including the Deploy Wizard.

But I will play your games! I created a new key with the name of "Xtreme ToolkitPro v18.0.1" per your example, but what do I place in the data field?

Where do I enter the "Compact Installation" or "custom installation without vc6 project files" on ToolkitPro installation. I don't see either?

After installation you can find  vc6 project files.

look at red rectangles on screenshot. Do you have the same options in Install wizard ?  Have you installed VS 6.0 ?

olebed wrote: Have you installed MS Visual Studio 6.0 before ToolkitPro installation ?

UPD:  you can download this big  image or just zoom web page to see text.  Screenshots have next order 

1 2 3
4 5 6 
7 8 9

Does your Win10 computer have installed Visual Studio 6.0 ?

One more thought, everything worked perfectly until release 1730. That's when all the trouble with the Deploy Wizard started. If I remember correctly they messed around with it and finally got working. The same thing is going on with this release.

Yes it was checked. Lets go back to the beginning, I logged onto the Codejock site, and downloaded the "Codejock.ToolkitPro.MFC.18.0.1.exe" module to my computer.

I ran that, entered the Product Serial Number then where I wanted to place the files on my computer. I then advanced to the "Select Components" panel where I checked the "Visual Studio Components" and selected the Optional Components which I only selected "Include Deprecated Classes". I then advanced to the "Ready to Install" panel where I selected the "Install" button. It then installed all the extracted files. Note that I later checked that all the files required to compile 18.0.1 were installed in the directory I specified.

It then started the "Completing the Xtreme ToolkitPro Setup Wizard". I unchecked the "Notify me of product news and Updates" and left checked the "Launch Deployment Wizard" then I pressed the "Finish" button.

The "Launch Deployment Wizard" started and then displayed the message "Error locating installation project files, aborting"

So what did I do wrong that resulted the Deployment wizard to abort?

Kenneth wrote: .. Note that the image above states "You may run this program at any time by selecting "Launch Deploy Wizard" from the "Codejock Software" start menu group". Where is this on Windows 10?

Deploy Wizard needs  project files  *_vc60.dsp and *_vc60.dsw. If they exist then you can build library and samples even by yourself. Many customers do this to include new fixes in source which posted on forum. Also DeployWizard checks keys in registry - license and path to installation folder.

I want your confirmation for every step  to find out problem.
You haven't answer is project files exist (*_vc60.dsp and *_vc60.dsw for VS 6.0)

olebed wrote: After installation you can find  vc6 project files.

That is why Deploy Wizard can't start. Now We need to investigate why installer haven't copy project files. If you select  "Visual Studio 6.0 Projects" during installation then problem can be in Installer. However I have tried Installer on virtual Win10 without problems (except case when I don't check "VS 6.0 Projects"). Also I haven't seen any similar problems with DeployWizard in support or forum.

Try to reinstall VS 6.0    description from Kirk Stowell

Please try to uninstall all previous versions of ToolkitPro, manually remove Codejock from Visual Studio paths, and close all instances of VS, then reinstall v18.0.1.

Also you can try on pure Windows10 (maybe on virtual machine).

DeployWizard needs  project files to start. It can't compile  cpp files without settings from project files. Problem in Installer, not in Deploy.

Which brings up another question, do you have the Microsoft Visual Studio C++ 6.0 on Windows 10 to test with?

Yes, and that's why I said we were talking past each other. The key statement is "Microsoft Visual Studio C++ 6.0". Take note of the version 6.0. That version cannot be detected by vswhere! It is a very old version of Visual Studio C++. So if you don't have the Visual Studio c++ 6.0 version, you cannot duplicate my problem!

Prior to 17.3.0 Kirk was using something else that detected the old 6.0 version. Then when he went to 17.30 I was getting problems much like I am now. Finally he fixed that version so it started working again.

Now he using vswhere (which cannot detect very old versions of the Visual C++) and I am back to failing again.

I just got through doing it and I still get the fail message. Is there anything I can check in my copy of Microsoft Visual Studio C++ to see if it is being detected by the 18.0.1 version?

If you are able to contact Kirk, ask him how he detects the Microsoft Visual Studio C++ 6.0 in Windows 10 so I can make sure what he expects is in mine. I know it worked when I compiled the 1730 project, but he could have changed something when he did the 1801 project.

That's the only thing that is different between my system and yours as it relates to compiling the Codejock projects.

You keep referring to the project files and in order to get them, you have to have found Microsoft Visual C++ 6.0 so that seems to be the key!

I went back and used the full default installation path as above and it makes no difference.

It looks like no one has a clue on how the Microsoft Visual C++ 6.0 is being detected, so we have to just wait on Kirk.

I tested taking defaults and it ran as before, aborting with the same message I always get. I then looked for the project files, and as you can see, they are not there. Why?

Yes, I did have the box checked to request "Visual Studio Projects" and Optional Components.

Can I get the source to the Deploy Wizard or all the conditions that produces the message "Error locating project files, aborting." so I can find the problem myself?