Working with push/pull projects with multiple remote contexts

A push/pull project with multiple remote context consists of a local project that gets associated with a [current] remote location as well as one or more additional remote locations. These locations are defined as contexts so that additional information can be defined for the remote location. This allows for the manual or automatic pushing of local resources in a project to their corresponding remote locations as well as the manual or automatic pulling of remote resources from the [current] context back to the local project. The remote contexts determine where builds should be run and where the resulting build output should reside. The local-to-remote location mapping using the [current] context also allows for good integration between tools that are available, such as the debugger and performance tools. For example, because the mapping indicates where build output should reside, it is easy to remotely launch a debugger engine with the right input while the corresponding local project source code can be used for setting breakpoints, stepping and other analysis tool functionality.

About this task

A local push/pull project with multiple remote locations approach consists of the following features:
  1. A 1-to-1 mapping between a local project (or other resource) and a set of remote contexts.
  2. The ability to push and pull resources between a local project (or other resource) and its corresponding remote contexts.
  3. Actions that can be performed on the local project (or other resource).
  4. Actions that can be performed on a single remote context.
  5. Actions that can be performed on the set of remote contexts for a given local project (or other resource).
  6. Views for each of the above features that:

Feedback