Best practice: New PC and existing projects bound to TFS
Posted: Wed Feb 08, 2017 3:48 pm
I'll be getting a new laptop soon and want to know how this will affect my existing (24) Flare Projects that are bound to Team Foundation source control. I'm using Flare 2017 and Visual Studio 2010. I am a single author and I don't use any global project files.
What is the best practice when I get my new PC? Will I re-map my Flare project to identical folder locations on my new PC as I had on my old PC? Should I un-bind my projects now on my old PC and re-bind on the new PC?
I don't know what should be done or from where (Flare or Visual Studio).
Help, I'm really confused by Team Foundation and since I have 24 active Flare Projects bound to source control, I need to do this the right way.
What is the best practice when I get my new PC? Will I re-map my Flare project to identical folder locations on my new PC as I had on my old PC? Should I un-bind my projects now on my old PC and re-bind on the new PC?
I don't know what should be done or from where (Flare or Visual Studio).
Help, I'm really confused by Team Foundation and since I have 24 active Flare Projects bound to source control, I need to do this the right way.