No announcement yet.

Local BC sessions

  • Filter
  • Time
  • Show
Clear All
new posts

  • Local BC sessions

    Organizing sessions in folders helps, but I think that a decentralized approach would be more flexible and less confusing in many cases. I have lots of projects, and for most of them I have BC sessions. This not only gives a annoying long list of sessions, but even worse does not work if I must work on different version of the project (e.g. do testing or bug fix in old releases), since the session contain all absolute pathes! Instead of a long list of global session I would like to store the session for a specific project where the project is, and open BC by double click on that session. So the session is stored with the project, as it should be, and if other colleagues check out the project they will have the needed BC sessions directly available, and since all pathes must be relative to this local session file, it would work regardless of on which place the project was checked out or copied.