Hello everybody,

finally we can start migrating some applications built with PB 12.5 to PB 2022 R2!

Now I think about how to migrate - or create newly - the working copies, one for each app. We already had started to work with SVN repositories using the AgentSVN interface. We have one repo for each app plus one shared repo. Workspace files were not added yet to the app repo's. The app repo's all have the same structure: A single target file in the root and a Sub-Dir for each PBL, but PBL's itself were not committed of course. Each sub dir contains a PBG file, rather. In addition: All working copies point to that shared repo by using some svn:externals properties. - That setup worked all fine, but of course we want PB's builtin SVN interface now.

Now I'd appreciate advice on how to start. I see I can create a new workspace inside an app's working copy - add the target - add the workspace to source control - but at that point I'm not sure if I should proceed as PB announces it would store the complete working copy in a new "folder with the workspace name" - I would not like that very much. Is there a more flexible way?

And in general: Does PB support that "externals" property at all?

Further: Some picture files are part of the qpplications. We had managed to keep them in the same repo's using Tortoise . Will PB tolerate Tortoise operations executed against the same repo's he manages it's application in?

Would be great if someone could provide advice on that. Thanks!