You are not logged in.
Having imported the file straight from the old workspace, however, actually did make a copy, did it not? Meaning, I am not in jeopardy of losing my work when I blow away the old installation directory, correct?
Yes, you can import the older project into the new TOS using the way: launch TOS, then import the old project from the exist workspace.
Ok, thanks for providing the preferred option. Having imported the file straight from the old workspace, however, actually did make a copy, did it not? Meaning, I am not in jeopardy of losing my work when I blow away the old installation directory, correct?
To migrate a old project to a new version of TOS, Simply follow the steps:
1.Click on the 'Export projects' button to export your project. (see screenshot1)
2.Import it into the new version of TOS.
To specify the workspace path, see topic:6977.
Ok I've got it! My "workspace" is under the TOS installation directory which I smartly tucked under C:\Program Files the first time (3.0) but misunderstood the installation dialog box the next and put under C:\.
So what I found worked for me was to import only the required items and meta from the old workspace directly. I don't know whether this is the best way to have done it, but it did it.
I built only a couple, simple jobs in 3.0-rc, and I built it all in a default Demo project in the "local" repository. However, I can't seem to locate those old jobs when I go to Import..
Where is the old "local" repository?? Did I have the option to define it somewhere custom (like a home directory on the network), and if so, how do I view properties of that repository to discover it?