Getting 'Object reference not set to an instance of an object.' exception

[terryaney]

I have a compiled context doing a simple query:

Profiles.Where( p => p.Client.cName == "AnnArbor" ).DumpPlan();

And it throws the exception. Not much information in the exception. Let me know what other information I can provide to help.

Trace:

at ExecutionPlanVisualizer.QueryPlanVisualizer.DumpPlan[T](IQueryable`1 queryable, Boolean dumpData)
at UserQuery
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[terryaney]

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

[borislitvak]

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

[Giorgi]

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

[terryaney]

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 notifications@github.com 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)

[Giorgi]

@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.

[Giorgi]

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

[borislitvak]

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?

[Giorgi]

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