Talk:IBM VisualAge C++ 3.0 Workframe

While I still use the VAC/C++ compiler, debugger and tools, I do not use the "workframe" any more. While I used to like the functionality very much, I did not like the fact that (due to the WPS integration!) the projects were not portable! Which means you cannot send a full "project package" to somebody else, or after reinstalling OS/2 or eComStation on a new computer you would have to generate all projects from scratch - and remembering all the settings! On the other hands, in terms of features and functionality I would always prefer this workframe to any other I know!

Restoring "project" objects
Some "tricks" to make the re-creation of a set of "projects less cumbersome. The point is that actually the Workframe "projects" DO contain all necessary settings, so they SHOULD actually be able to work on another system too! The problem is with the inheritance: This is stored as a WPS "file handle" of the parent "project" within the project. This handle is the item that makes "projects" unportable!

What you can do to make life at least somewhat easier:


 * First of all, never touch the standard base "project" at all, but derive an own "base project" from it. This may be changed or not, but you will keep it even in case of a fresh installation.
 * Derive e.g. a "exe program" project from your own base project, and then derive all actual projects generating exe files from that common base. Etc.
 * Now comes the "trick": If you just reinstall VAC/C++ 3.0 on a system with existing projects, the only thing you have to do is: Open the "settings" of your own "base project", go to the "Inheritance" page, remove the (probably completely wrong) reference you find there (that can be ANY file on your computer actually!) and add the right VAC "base project" instead. Since all other file handles in your project were not touched by the new installation, this will restore your whole projects setup!
 * If you copy a whole set of projects to another computer, or if you reinstalled your system completely, you will have to repeat that same "parent restoration" procedure for all your projects.