Selected VCS operations will be supported for
whole  Portfolio:
    * opening from VCS 
    * adding to VCS 
    * updating and committing 
For the first version we don't plan to handle the
Portfolio as a whole transparently. We plan just
to apply the functionality mentioned for projects
repeatedly on all projects in the Portfolio. In
case of Getting Portfolio from VCS, the user must
know where all the Portfolio projects lie in the
VCS repository, this information is not stored in
the Portfolio file. The user will be able to
specify more roots to "checkout". After locating
the Portfolio file, the IDE will open it and
inform the user about all missing projects. These
projects will be marked somehow in the explorer.
The user will be able to restore the projects.
 
This limited support can work quite smoothly if
one simple condition is fulfilled. The structure
of projects storage of a Portfolio must be the
same on the local disk as in the repository (in
relative paths). Even better is if all the
projects lie on the same directory level so they
can be got from VCS just as one directory root.