Please note that our profiler can be used only with data models built with OpenAccess ORM and it is actually only a visual presentation of the log data that OpenAccess generates during runtime. The profiler itself does not listen to or profile any database connections but is attached to the OpenAccess context of the running application.
Having this in mind, I assume that if you decide to use OpenAccess as ORM for your project, it would be better to use the tracking API of OpenAccess directly by implementing a trace listener
or providing a text writer
to the context instance directly. Then you can display the information in the most appropriate way in your user interface.
Hope that helps.