StevenTCramer@gmail.com Posted November 14, 2013 Report Share Posted November 14, 2013 I have created the following Test scenario: 3 repos 1. TestParent 2. TestChild1 3. TestChild2 Create the Test Parent workspace in C:\Plastic\TestParent then add xlinks to the parent pointing to TestChild1 and TestChild2 and add files to each see attached image One can see the branching via the explorers for all 3 repos. The file directory looks as follows. This all looks good. But if one selects "Switch workspace to this changeset" on a linked branch explorer. The files from that repo get added to the root of the workspace as shown vs adding them into the linked location. switching workspace from the Parent branchexplorer puts the files back in normal location. So should one be able to switch the workspace from a linked branch explorer? Link to comment Share on other sites More sharing options...
manu Posted November 15, 2013 Report Share Posted November 15, 2013 Hi, well, what's happening makes sense, the directories (xlinks) and the files inside disappears (and child2File1.txt appears) due to you are switching to a changeset of a different repository, so then, the content of the other repository is loaded... You have to perform the switch to branch operation from the TestParent repository, as this is a test don't be afraid of committing, you'll see how the changes inside the items of the xlinks are propagated to the remote repository. Test the branching and merging, see how the expansion rules works, it really rocks. Review this blogpost in order to learn the basis -> http://codicesoftware.blogspot.com/2011/12/how-to-link-repositories-using-xlinks.html Link to comment Share on other sites More sharing options...
StevenTCramer@gmail.com Posted November 15, 2013 Author Report Share Posted November 15, 2013 Yes I did play with a bit and it does Rock. In my case the directory location is being referenced by another program so switching to a child workspace repo other than via the Parent messes up the referenced program. It would be nice if I could disable that ability on xlinks for the project so I don't accidentally do it. The reason I am using xlinks is to allow for an entire overview of development in all projects and xlinks does an excellent job of this. Although code reviews from xlinks do not propagate up to the parent. Which would be nice feature. Link to comment Share on other sites More sharing options...
manu Posted November 15, 2013 Report Share Posted November 15, 2013 Yes, the code reviews for xlinked content is in our roadmap Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.