I double checked and is running in debug mode, and also is on the same machine (development).
I am running from Visual Studio 2019, debug time. Running also everything as administrator. The profiler is silent and no activity recorded whatsoever. Clicked on the button "record to snapshot" but nothing happens.
Wondering if this is because I am using LLBL Gen Pro 5.3 and the Profiler is 2.0 ?
No it should work fine. It wraps the factory you specify and the runtime simply uses the wrapped factory. All activity on the objects is then send over a named pipe to the client. I don't think firewalls locally block named pipes.
If you create a simple console app with the same generated code and try to read an entity from the database using the same initialization code as your webapp, do you see activity then?
What changes did you make to the adapter? The main issue is that if the factory isn't wrapped, (which is done by the interceptor initialize), the original factory is used and therefore no calls are intercepted.
Also, as v2.0.2 of ormprofiler is free for you, could you try the v2 version and see if it fixes it for you?
If you grab the SqlClient factory from DbProviderFactories:
var factory = DbProviderFactories.GetFactory("System.Data.SqlClient");
and check the type (after InterceptorCore is called), is it a Profiler* type or is it System.Data.SqlClient.SqlClientFactory ? (please write out the type in full, as the tostring can be misleading)
If it's SqlClientFactory, the overwriting of the DbProviderFactory table hasn't succeeded, and the factory isn't wrapped (causing no data to be send). If the type is a Profiler* type, the factory is wrapped and the data might not be accepted by the client, which is the case if the client runs on another machine (as the connection is over a named pipe).
Other than that it's weird, as here everything works fine in that kind of setups.