|
These calls are explicit for 3GL-written applications, such as "C" or "C++" (if not using special libraries, like ATL, for example). 4GL-written applications, such as Visual Basic and Powerbuilder and 3GL applications using libraries make these call implicitly, through specialized language constructs or library objects.
|
|
The task of tracing COM-related calls the application is making becomes very important for:
Debugging COM applications
Testing applications using COM
Resolving performance problems
|
|
For simple 3GL-written applications the tracing can be done by inserting tracing statements for every call. If the 3GL application is very complex this strategy is usually not acceptable, as inserting tracing statements becomes a project by itself. For 4GL situations and libraries inserting trace statements for low level calls is usually not an option.
|
OLESPY can trace COM API functions as well as interface methods for any COM client application launched by OLESPY.
OLESPY is based on the proprietary technology
developed by Kogosoft Corporation.
|
OLESPY is an MDI application with intuitive and powerful user Interface . Multiple tracing sheets can be opened at the same time. Trace information includes:
- COM function or interface method's name
- Return code
- Timestamp
- Values of arguments
- Execution time
|
![[OLESPY]](./img/ole_anm1.gif)
