You use this dialog to view or modify the current settings for the various properties of a data source project.
To open this dialog, right-click the data source project in Solution Explorer and select Properties.
To modify a property setting, change the property value and click the OK button.
The exact properties vary depending on the specific data source project type.
Note: The following properties apply to all data source project types.
Application
| Property Name | Description |
|---|---|
| Localizable | If true, include model annotation support for localization; automatically create localization resource files for each Client, Server, and Common message. This only applies to MVC presentations. Refer to Localization Support for MVC. |
Note: The following properties are created when you create a data source project. These are the read-only properties, which provide information about the data source project and the resulting assembly that is built:
Assembly Name
Default Namespace
Output Type
Build
Property Name | Description |
|---|---|
Build DLL In Parallel | If True and if building the data source DLL incrementally, the compile operations will be performed in parallel to reduce the overall build time. The default is True for new projects. |
Build DLL Incrementally (Debug) | If True, a Debug build will compile each ePortal message class file into a netmodule file, and the individual netmodule files are linked with the orchestration code to create the data source DLL. If False, all ePortal message class files and the orchestration code are compiled and linked in one step whenever any message or the orchestration changes. Setting this value to True may increase the full build time, but should significantly reduce the time of subsequent builds for solutions with many messages. The default is False for new projects. For .NET Core Web API projects, set the value as False. This is because the netmodules are not supported by the .NET Core Web API projects. |
Build DLL Incrementally (Release) | If True, a Release build compiles each ePortal message class file into a netmodule file, and the individual netmodule files are linked with the orchestration code to create the data source DLL. If False, all ePortal message class files and the orchestration code are compiled and linked in one step whenever any message or the orchestration changes. Setting this value to True may increase the full build time, but should significantly reduce the time of subsequent builds for solutions with many messages. The default is False. For .NET Core Web API projects, set the value as False. This is because the netmodules are not supported by the .NET Core Web API projects. |
Build DLL MVC Core | If True, a build will compile each ePortal message class to create the data source DLL that can be used in a .NET Core MVC presentation project. If False, a build will compile each ePortal message class to create the data source DLL that can be used in a .NET MVC Framework presentation project. |
For more information about Build properties, refer to Building the Solution.
Message Handling
| Property Name | Description |
|---|---|
| Auto Create Client Message | If this property is set to True, then ePortal will create a corresponding client message with the same name whenever a server message is created. If this property is False, then ePortal will not create a corresponding client message when a server message is created. If this property is False, you will need to explicitly create your own client messages. Refer to Creating Client Messages. This property defaults to True for the following data source types: MCP T27, OS 2200 UTS, OS 2200 Open DTP, and OS 2200 TIP. This property defaults to False for the MCP COBOL data source type. Notes:
|
| Auto Recreate Client Message | If this property is set to True, then ePortal will overwrite an existing corresponding client message with the same name whenever you save changes to a server message. If this property is False, then ePortal will not overwrite the corresponding client message when a server message is updated. Note that if this property is True, any changes you make to your server message are propagated to the corresponding client message. However, if you have made changes to your client message, these changes will be lost if you later update the corresponding server message. Conversely, if this property is False and you make a change to your server message, the change is not propagated to the corresponding client message. If the change you make to your server message is also required in the corresponding client message, then you will need to modify the client message. Refer to Modifying Client Messages. This property defaults to True for the following data source types: MCP T27, OS 2200 UTS, OS 2200 Open DTP, OS 2200 TIP, and AB Suite/EAE. This property defaults to False for the MCP COBOL data source type. Notes:
|
Preserve Client Message Changes | When a client message is being recreated, this option allows you to preserve any modified field properties in the existing client message, so that the custom changes are not overwritten. If this option is set to True, when a client message is automatically recreated from a server message, any changes that were manually applied to the fields in a client message will be preserved. The property assumes that the AccessType and DataType of the field have not changed; otherwise, the field properties will be overwritten with new information from the updated server message. If this option is set to False, the existing client message will be overwritten when the AutoRecreateClient option is selected. |
Runtime Error Checks Performed | The error checking to perform at runtime when setting a client or server message field. For more information, refer to Runtime Error Checking for Message Fields. Note: If you change the value of this setting, you should select Rebuild Solution from the Build menu to ensure that all files are regenerated using the new setting. Refer to Rebuilding the Solution for more information. |
Add Data Order to Class Members | If this property is set to True, a sequence order will be applied to the members of the generated client message class. This sequence will match the order in which the fields are defined in the client message. The sequence also reflects the order of the fields defined in the ClearPath Application metadata (for example, COBOL Record definitions). Additionally, this sequence order will be preserved when the client messages are serialized instead of defaulting to an alphabetical order. Note: The default value is set to False.If you change the value of this setting, you should select Rebuild Solution from the Build menu to ensure that all files are regenerated using the new setting. Refer to Rebuilding the Solution for more information. |
Project
| Property Name | Description |
|---|---|
Target Framework | This is the version of the .NET framework that this data source project targets. You can modify this value to change the .NET framework version; however, if you change the target framework version:
|
Note: The following properties are created when you create a data source project. These are the read-only properties, which provide information about the data source project and the resulting assembly that is built:
Output File
Project File
Project Folder
Refer to the following topics for additional properties that are specific to particular data source project types: