ILOG Rules for .NET User Guides > Rule Studio > Storing and Sharing Rules > Using a Source Control Provider > Adding Business Object Models to Source Control

You can manage business object models using an integrated source control provider.

To add a business object model to source control

If the solution containing the class library project(s) for the business object model is not under source control:

If the solution is already under source control:

This adds all the items in the class library project, including those specific to business object models, such as the Model.bmx file.

The Model.bmx File

The Model.bmx file is an XML representation of the business object model. There is a Model.bmx file for each class library that has been imported into the Business Object Model View. You can see the Model.bmx file in the Solution Explorer using the Show All Files command. The Model.bmx file is an item of the BomAssemblyInfo file.

To check out (and check in) the Model.bmx file you must check out its parent, the BomAssemblyInfo file.

Note
It is recommended that you check out the Model.bmx file before building a business object model to incorporate changes to the signatures of the members and types. If you do not check out Model.bmx and there are changes to the signatures to take into account, Model.bmx is automatically checked out for you. This automatic check out generates a warning message from Visual Studio .NET that you can safely ignore.

The XML Schema for the Model.bmx file is described in the Reference section.

Comparing Business Object Models

You can use your source control provider to compare versions of a business object model by comparing versions of the Model.bmx file.

See Also

Adding Rule Projects to Source Control