ILOG Rules for .NET User Guides > Using ILOG Rule Execution Server for .NET > Reference: Rule Execution Management Using MSBuild > Task Mappings

In a production environment, it is common to automate deployment and other managerial tasks using a build tool. MSBuild is a .NET build tool, and Rule Execution Server for .NET provides a number of MSBuild tasks to automate RuleApp management.

MSBuild is included in the SDK part of .NET Framework 2.0, so you do not normally need to do anything to set it up. You will find the MSBuild.exe file in the relevant Framework version 2.0 folder on the drive where the framework is installed. For example:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Using the command prompt, you should be able to call MSBuild from any folder.

To use the Rule Execution Server for .NET MSBuild tasks in an MSBuild project file, you need to import the task and declare the class path, the mapping between the .NET classes, and the keywords of the tasks.

The MSBuild.ExecutionServer.Tasks.Targets file is located in the <InstallDir>\bin\Public Assemblies directory.

The Target file defines the following mappings for RuleApp management tasks:

The Target file defines the following mappings for persistence administrative tasks:

The development and administrative MSBuild tasks and Management Service communicate using the Secured WCF TCP Binding.

The Target file defines the following mapping for Execution Service tasks:

See Also

CreateRuleApp Task | DeployRuleApp Task | FetchRuleApp Task | UndeployRuleApp Task | CreatePersistenceSchema Task | DropPersistenceSchema Task | BackupRuleApps Task | RestoreRuleApps Task | CreateExecutionUnitBaseDirectory Task | Managing Rule Execution Server