Source control (TFS) and moving project's local location?
Posted: Fri Oct 28, 2016 10:52 am
Here's the quick rundown of the problem we're facing here.
I was the only tech writer on staff when we started using Flare, so set up my projects in the My Documents folder on my local PC. This includes a Style Guide that all projects are linked to via Global Project Linking. Everything is bound to TFS source control.
We've since hired a new tech writer. He downloaded all the projects from source control, also located in his My Documents folder.
The problem we just noticed is that the path to the My Documents folder contains our usernames (C:\Users\jsandora\Documents\help files\madcap\StyleGuide). This is causing a problem with the Global Project Linking since the path located in the Import file for the Style Guide is the one on MY computer - so it contains my username. So when he kicks off new builds in the projects, the Style Guide files (stylesheets, page layouts, etc) aren't getting imported since the Style Guide project path doesn't exist on his machine.
Our solution is to just create a folder structure from the root instead of the Documents (C:\help files\madcap\) and put all our projects in there. If we use the same structure, there's no problems with incorrect reference paths or whatever.
So my question is, what's the best way to move these projects on our local machines?
- Disconnect project from Source Control, move it locally, Reconnect to Source Control
- Disconnect project from Source Control, download it from Source Control in the new location
- Just move projects without disconnecting
Since that Import file has the username path, I'm assuming we'll have to update that link in each moved project regardless of which method we use. I just want to know which is the best way to move stuff locally so it doesn't screw up Source Control and such.
Thanks ...
I was the only tech writer on staff when we started using Flare, so set up my projects in the My Documents folder on my local PC. This includes a Style Guide that all projects are linked to via Global Project Linking. Everything is bound to TFS source control.
We've since hired a new tech writer. He downloaded all the projects from source control, also located in his My Documents folder.
The problem we just noticed is that the path to the My Documents folder contains our usernames (C:\Users\jsandora\Documents\help files\madcap\StyleGuide). This is causing a problem with the Global Project Linking since the path located in the Import file for the Style Guide is the one on MY computer - so it contains my username. So when he kicks off new builds in the projects, the Style Guide files (stylesheets, page layouts, etc) aren't getting imported since the Style Guide project path doesn't exist on his machine.
Our solution is to just create a folder structure from the root instead of the Documents (C:\help files\madcap\) and put all our projects in there. If we use the same structure, there's no problems with incorrect reference paths or whatever.
So my question is, what's the best way to move these projects on our local machines?
- Disconnect project from Source Control, move it locally, Reconnect to Source Control
- Disconnect project from Source Control, download it from Source Control in the new location
- Just move projects without disconnecting
Since that Import file has the username path, I'm assuming we'll have to update that link in each moved project regardless of which method we use. I just want to know which is the best way to move stuff locally so it doesn't screw up Source Control and such.
Thanks ...