Advice For Managing Configurations in VC6.0

I'm looking for some advice on how to intelligently manage configurations in Visual Studio 6.0. That advice can come in to form of methodology or 3rd party tools that help with the problem. The problem is not a problem in Visual Studio 2003 and 2005. Both of these IDEs have the concept of "Solution Configurations" in the configuration manager. As a result, if I have multiple projects with multiple configurations, I can group them in a managable way using this configuration manager. For example lets say I have 3 projects: Project 1, Project 2, and Project 3. Project 3 is dependent on Projects 1 and 2. Project 1 and 2 have 4 configurations Debug MT, Debug MD, Release MT, Release MD. Project 3 has 8 different configurations: Debug Trial MT, Debug Trial MD, Release Trial MT, Release Trial MD, Debug Normal MT, Debug Normal MD, Release Normal MT, Release Normal MD. Now, using VS2003, we can easily create a solution configuration for each build of Project 3 and set up the correct builds for each of it's components. For example we might create a solution configuration called "Release Normal MT" which consists of Release MT of Projects 1+2. The question we have is how can and should this be done in Visual Studio 6.0? We would like set up these values using project depdencies that do not require us to edit the link settings of each individiual project. Can you help? Fast turn around will be accepted first. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform vs6.0