Sorry for the delayed reply, we are quite busy with the preparation of the new service pack.
The OpenAccess profiler is used absolutely the same way with LocalDB as with any other backend:
- Enable logging data in the rlinq file, as described here
. You could try a higher log level like Verbose
in order to get more messages.
- Start the profiler service at the beginning of the application execution.
- Connect the profiler using localhost
as server name (if the application is running on your local machine), the port specified in the StartProfilerService method call and the connection string name used in the application.
Please note that if the application has not been started yet, the profiler will not be able to connect and will display errors. However, it will continue trying to connect and if you start the application later, you should be able to see the log data.
If the application is running and an OpenAccessContext instance is already created (a connection to the database has been established), you should even be able to see the connection string in the combobox of the Profiler's Open Connection
Hope that helps.
the Telerik team
OpenAccess ORM Q2'12 Now Available! Get your hands on all the new stuff