Topics x-ed out

I think it's best to have the entire project checked out of source control before upgrading. But this can be done manually through source control before opening the project in RH.

My testing on upgrading RH6 to RH8 was a little flaky and sometimes it did take a couple of attempts - checkout, upgrade, fail, delete off disk, get old version using Label (seems to be the only reliable method in VSS), upgrade, worked this time, check in.

I recommend ensuring everything is shipshape in the old version before upgrading - tidying up links and unused files, deleting the project off disk and getting all files afresh, to make sure there aren't any broken links hiding because of legacy files and cached info in the cpd. But it should all still work if you don't have an old version to go back to for the tidy up.

Possibly just deleting the cpd to ensure it doesn't try to add anything back into the project incorrectly might help. Also maybe manually ensure all files are writable after checking out of source control - VSS sometimes didn't seem to mark files correctly.

HTH

Amebr

P.S. You shouldn't need to check it in as a new project, although you can if you want. Also, it wouldn't hurt to double-check that all new files have been added to source control correctly (not forgetting to EXCLUDE the cpd and pss as usual. I can't remember if there are any other new ones that should be left out for RH8).