• No results found

Adding a Solution to MKS Integrity

By adding a solution to MKS Integrity, you automatically add all of the projects and files contained in that solution.

When adding a solution, subprojects are created for Web projects. However, by default, subprojects are not created for non-Web projects. To create subprojects for non-Web projects, before performing this procedure, select the Create Subprojects option in Preferences Configurations dialog box for the Add Members command.

NOTE If you select the Create Subprojects option in Preferences Configurations

dialog box for the Add Members command after adding non-Web projects, and then

add new members to those projects, see “Troubleshooting” on page 134 to resolve the issue. If you do not resolve the issue, you will encounter Sandbox detection problems when performing operations in the integration.

When adding a solution, all files in the solution are added as members. For information on the recommended project structure, see “Best Practices for Solution Root Project Structure” on page 117.

A Sandbox is automatically created for the solution, containing corresponding subSandboxes for the subprojects.

IMPORTANT If you added a solution to MKS Integrity from outside of Visual Studio .NET instead of as described in this procedure, you must bind the files by selecting

Source Control > Change Source Control. Then from the Change Source Control

dialog box, select the files in the list, and then click Bind.

To add a solution to MKS Integrity using Visual Studio .NET

1 In Visual Studio .NET 2003, select the solution you want to put under version control. 2 For a Visual Studio .NET 2003 solution, select File > Source Control > Add Solution to

Source Control. The Create Project Wizard displays.

NOTE If the administrator needs to modify the ChangePackageEnabled policy on the MKS Integrity Server, all active change packages should be in a closed state before making the modification. The administrator should advise users accordingly. If any active change packages remain open during a policy modification, the

3 For the project you originally selected, choose one of the available options:

Create a new project and click Finish. The Specify Project dialog box displays. In the File name field, specify the name of the project you want to create on the

MKS Integrity Server.

Create as a subproject of an existing project and click Next. In the Project Name field, specify the name of the existing MKS Integrity configuration management project or click Browse to select it from the list of existing registered projects on the MKS Integrity Server. In the Subproject Name field, specify the name of the subproject you are creating. (By default, the name is <solution name>.root.) To have the changes take effect, click Finish.

Create as a subproject of a new root project and click Next. For the Project Name field, click Create New to create the new root project on the MKS Integrity Server. The Specify Project dialog box displays. In the File name field, enter the name of the new root project and click OK to accept the changes. To have the changes take effect, click Finish.

For example, for three related projects (Lunar1, Solar2, and Stellar3) that are not currently under MKS Integrity control, you begin by selecting the third option to Create as a subproject of a new root project. Select the Lunar1 project and create it as a subproject at a new project root defined by you, for example, System. The next project (Solar2) can then be created by selecting the second option, Create as a subproject of an existing project. Because Solar2 is a related project, it is created as a subproject of the existing top level MKS Integrity configuration management project, System. For the remaining project, Stellar3, you repeat the process used for Solar2, and create it as a subproject of the existing System project.

NOTE By default, if you create a chain of directories, all subfolders in the directory are also created as subprojects. If a subfolder does not include a .pj file,

project.pj is also added to the subproject string.

4 If your project contains files, the Create Archive dialog box displays. Modify the Create Archive options as described in the MKS Integrity Client 2009 User Guide or online help.

NOTE If MKS Integrity finds an existing archive, the Existing archive detected

dialog displays. For more information on sharing archives, see the MKS Integrity Client 2009 User Guide or online help.

For each Web project, subprojects are created using the Web project names.

Each file under version control corresponding to a MKS Integrity member is marked in the Solution Explorer with the icon.

MKS Integrity also automatically creates a Sandbox with the project name in your .NET workspace. If an existing Sandbox is detected in the solution directory, the Get SCC

Project Path dialog box displays, asking you if you want to use the existing Sandbox for source control operations.

NOTE If you want to use a new Sandbox, click No to return to the Create Project Wizard.

To use the existing Sandbox for source control operations, click Yes. The Solution Root Location Wizard displays.

5 The solution root represents the location where future Web projects will be created. Select from the available options:

 Use the identified project or click Browse to select another project.  Create a new project or subproject on the MKS Integrity Server.  Disable solution root functionality for this solution.

6 To use the selected solution root option, click Finish.