Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > ORM Profiler Section > Bugs & Issues> Not receiving anything
 

Pages: 1
Bugs & Issues
Not receiving anything
Page:1/1 

  Print all messages in this thread  
Poster Message
bvi
User



Location:

Joined on:
23-Feb-2015 11:43:40
Posted:
6 posts
# Posted on: 23-Feb-2015 11:50:08.  
We have a dot net 3.5 application with llbgen 2.6
We want to use the orm profiler

So i have copied and referenced the dll's, placed the initialize in the startup.
This step is done with no errors, i can see it when i debug.
Also i have placed in the config-file the <appSettings> part, this has no errors.

Then i first startup the ormprofiler, then the applicaiton and i receive no data.

What did i miss?
  Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
613 posts
# Posted on: 24-Feb-2015 09:42:02.  
Did you read the section about v2.6 in the manual?

Quote:
LLBLGen Pro v2.6 specific

ORM Profiler is supported on LLBLGen Pro Runtime Framework v3.x or higher. However, it will also work with LLBLGen Pro v2.6 runtime framework powered applications, as long as the query engine is targeting SQL Server.

So, do you use sqlserver ?


Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
bvi
User



Location:

Joined on:
23-Feb-2015 11:43:40
Posted:
6 posts
# Posted on: 24-Feb-2015 09:43:48.  
Yes, we are using sql server
  Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
613 posts
# Posted on: 25-Feb-2015 09:22:06.  
bvi wrote:
Yes, we are using sql server

Ok, are client and app running on the same machine? The interceptor init is called?


Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
bvi
User



Location:

Joined on:
23-Feb-2015 11:43:40
Posted:
6 posts
# Posted on: 25-Feb-2015 09:53:36.  
Yes, both.
  Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
613 posts
# Posted on: 25-Feb-2015 17:19:04.  
Ok, one last check: the call to the initializer has to be the first thing the application does. The thing is that it looks like the factory is already initialized before the interceptor is initialized (and it then doesn't work anymore). Also be sure to use the latest v2.6 runtime build.

Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
bvi
User



Location:

Joined on:
23-Feb-2015 11:43:40
Posted:
6 posts
# Posted on: 26-Feb-2015 09:53:39.  
OK, it is not the first thing the application does. We shall change it.
  Top
bvi
User



Location:

Joined on:
23-Feb-2015 11:43:40
Posted:
6 posts
# Posted on: 02-Mar-2015 08:35:12. Goto attachments  
The initializer is now the first thing we call. However, we now get the error:
"Unable to cast object of type 'SD.Tools.Ormprofiler.Interceptor.ProfilerDBConnection' to type 'System.Data.SqlClient.Sqlconnection'.


  Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
613 posts
# Posted on: 03-Mar-2015 09:32:41.  
bvi wrote:
The initializer is now the first thing we call. However, we now get the error:
"Unable to cast object of type 'SD.Tools.Ormprofiler.Interceptor.ProfilerDBConnection' to type 'System.Data.SqlClient.Sqlconnection'.

Then it's not the first thing you call or you instantiate SqlConnection objects somewhere? Be aware that if you have a static ctor, that is called first. If you do some data-access in that ctor the factory already gets initialized.

I don't recognize the code, is that your code? Is the 'ActualConnection' a DbConnection you created?
Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
bvi
User



Location:

Joined on:
23-Feb-2015 11:43:40
Posted:
6 posts
# Posted on: 03-Mar-2015 10:23:15.  
It works now. Thanks for your help.

  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.09082011 Final.