Getting 'Object reference not set to an instance of an object.' exception about linqpad.queryplanvisualizer HOT 8 CLOSED

Hmm, seems to work against the dynamically created context from LINQPad against same DB/table. Are compiled contexts supported?

from linqpad.queryplanvisualizer.

I can also report the above behavior on v4.57.02.
Did not check the dynamically created context part.

from linqpad.queryplanvisualizer.

@terryaney @borislitvak Do you use LINQ to SQL or Entity Framework typed data context?

from linqpad.queryplanvisualizer.

I use LINQ to SQL…I see you just made EF work on another comment. But I know we have code for our L2S stuff that leverages a DbContextInterceptor (or whatever it is called) so hopefully you can find that available to you as well.

On Mar 19, 2016, at 4:10 PM, Giorgi [email protected] wrote:

@terryaney https://github.com/terryaney @borislitvak https://github.com/borislitvak Do you use LINQ to SQL or Entity Framework typed data context?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub #4 (comment)

from linqpad.queryplanvisualizer.

@terryaney I don't remember any class which is able to intercept LINQ to SQL queries. I will see what I can do to make it work.

from linqpad.queryplanvisualizer.

This should be fixed now. Will publish a new release tomorrow.

from linqpad.queryplanvisualizer.

I am still having the same issue with LINQ to Entities, as this tool only supports EF6 contexts.
This is the reason the LinqPad created context words.
Is there any way to make the tool work for EF5?

from linqpad.queryplanvisualizer.

@borislitvak Can you create a test data context dll and attach it to this issue?

from linqpad.queryplanvisualizer.