The one with NetFull is indeed something you can't do: you have to use the normal automatic factory usage and don't need to register the factory manually, as it will obtain it from the DbProviderFactories table (it will wrap all factories there).
the manual wrapping of the factory is needed for .NET Core 2 only, as on .NET Core 2 there's no pre-defined DbProviderFactories table, you have to register the factory first manually anyway, so wrapping it using the interceptor is the easiest. The method InterceptorCore.Initialize(name, type) is only present in the .NET Core variant of the interceptor. So referencing .NETFull and then calling that method will lead to compile errors. You have to reference the .NET Core variant of the interceptor there. You mention you can't reference that one, could you elaborate why?
Registering the factory in RuntimeConfiguration using a .NET Full application and using the .NET Full version of the interceptor won't work indeed, as the llblgen pro runtime won't read the factory from the DbProviderFactories class as it already got the type it needs through the RuntimeConfiguration.
This is indeed something we could add to the .NET Full variant. We don't want to make it a single package with 2 dlls as the API is different and behavior is different: the normal interceptor method isn't available in the .NET Core variant, and that's deliberate (as there's not a central Dbproviderfactories table pre-configured, it has to be pre-filled by your application).
If you use RuntimeConfiguration in a .NET full app btw, you don't need to initialize the DQE with the DbProviderFactory, you can remove that line. If the factory's not present it will obtain it from the central DbProviderFactories table.
Where are you initializing the interceptor (i.e: FormLoad, etc.)
in the program startup before creating, loading, running the main form.
What is that you can't compile? What is the error?
When I try to reference the dotnet core interceptor, nu get doesn't complete the reference. I was trying that interceptor as an experiment since the data layer is dotnet standard.
Referencing the dotnet full interceptor does show the reference and the app compiles and works, but I see nothing in the profiler client.
Did you start the profiling en ORMProfiler?
I will retry this morning and make sure I did. If I did and I see no activity in the client, how can I trouble shoot that?
If you do, the DQE has the factory type and won't request one from DbProviderFactories, and therefore won't get a wrapped version (so nothing gets intercepted). If you omit that line, the DQE doesn't have a factory and therefore will obtain one from the DbProviderFactories, which is the wrapped on due to Interceptor.Initialize() and actions will be intercepted.
When I do this the profiler client (running on the same machine) doesn't show any traffic, but the application itself works.
How can I trouble shoot further?
First please make sure the line above is indeed not present in your program. You only have to pass the factory type on .NET core/standard (so the .net standard lib runs on .net core)