This project is read-only.

Avoid Workspace Mapping to Support Cross-Project Dependencies

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

In general, you should avoid dependencies that cross team projects and try to have all the related/dependent solutions/projects under the same team project. This reduces the need for build script customization. If you have a dependency, use project references to define it, or branch the dependency from a shared project into your project. You should avoid file references because they are more difficult to manage. The exception is when the dependent project is developed in parallel and you need real-time changes. In this case, you can consider using workspace mapping. However, you can still use branching in this case to create a buffer of isolation, if the dependent code is causing too many breaking changes.

Additional Resources

Last edited Jul 26, 2007 at 11:37 AM by prashantbansode, version 3


No comments yet.