Generate object API code for applications that will run on Windows Mobile.
From | Action |
---|---|
The Mobile Application Diagram | Right-click within the Mobile Application Diagram and select Generate Code. |
WorkSpace Navigator | Right-click the Mobile Application project folder that contains the mobile objects for which you are generating API code, and select Generate Code. |
Option | Description |
---|---|
Language | Select C#. |
Platform | Select the platform ( target device) from the drop-down list for which the device client code is intended.
|
Unwired Server | Specify a default Unwired Server connection profile to which the generated code connects at runtime. |
Server domain | Choose the domain to which the generated code will connect. If you specified an Unwired Server to which you previously connected successfully, the first domain in the list is chosen by default. You can enter a different domain manually. Note: This field is only enabled when an Unwired Server is selected.
|
Page size | Optionally, select the page size for the generated client code. If the page size is not set, the default page size is 16KB at runtime. The default is a proposed page size based on the selected MBO's attributes. The page size should be larger than the sum of all attribute lengths for any MBO that is included with all the MBOs selected, and must be valid for the database. If the page size is changed, but does not meet these guidelines, object queries that use string or binary attributes with a WHERE clause may fail. Note: This field is only enabled when an Unwired Server is selected. The page size option is not enabled for message-based applications.
|
Namespace |
Enter a namespace for C#.
Note: The namespace name should follow naming conventions for C#. Do not use ".com" in the namespace.
|
Destination | Specify the destination of the generated device client files. Enter (or Browse) to either a Project path (Mobile Application project) location or File system path location. Select Clean up destination before code generation to clean up the destination folder before generating the device client files. |
Replication-based | Select to use replication-based synchronization. |
Message-based | Select to use message-based synchronization. |
Backward compatible | Select so the generated code is compatible with the SUP 1.2 release. |