Build areas are an integral part of Dimensions Build. Build administrators should specify how developers work with Dimensions Build and set up build areas accordingly.
What needs to be done is each client developer should have their own solution stored on there client machine and should access it as necessary. The client solution is created by the developer as a blank solution and web projects are populated from Dimensions. They can validate the projects in the solution by looking at the 'show repository bindings'.
• Solution developers and customers wanting to merge custom changes they made to a process app in an earlier version of a solution into the same process app provided in a newer version of the solution . Information for these readers is found in Compare and Merge in SBM Composer [page 9].
Opening the solution from source control and selecting location for the contained web project, users must select a different HTTP work location for each development machine/ developer involved. HTTP locations for the web project should be under the default C:\Inetpub\wwwroot folder to avoid unexpected behavior from VS.NET.
• There is not a single build utility that can handle all development tools. This problem is becoming more apparent as developers turn to solutions such as Ant to solve more and more of their JAVA build
