| No | Synchronous Mode | Asynchronous Mode |
| 01 | DLL mode | Multi-process mode (spawned mode) |
| 02 | Application and Creo parametric do not perform concurrent operations | Creo Parametric & Plugin can perform concurrent operations |
| 03 | Application process is the child process of Creo parametric (xtop.exe) | Using remote procedure calls (rpc) for communication between the application and Creo Parametric |
| 04 | Application started by Creo parametric based on the registry file used in the auxiliary application | Application independently started and it can start the Creo or connect with existing Creo application |
| 05 | Application appears in auxiliary dialog box | Application will not appears in auxiliary dialog box |
| 06 | Application started by creo_initialize() and end by creo_terminate() functions | The application can have own main() or wmain() function |
| 07 | No communication gap due to the single process | Each process can send a message to the other to ask for some operations, but each wait for returning message that reports that operation is complete |
| 08 | No control states | Control states between the two processes, one of which is always in a wait state |
| 09 | Comparatively faster operations | The use of rpc in spawn mode to perform significantly slower than DLL mode |
| 10 | Creo Toolkit, J-Link, Web-link | Creo Toolkit, J-Link, VB-API |
