DbContext Autocomplete isn't working anymore on v4.43.06
Hi,
I might be going mad, but autocomplete doesn't seem to be working in v4.43.06
I have a premium licence and the queries are executing ok, but the autocomplete on parameters isn't working e.g.
But I'm pretty sure it previously autocompleted on pressing "." after b
I've tried using the short cut keys listed under Edit > Autocompletion to no avail.
Any ideas?
I might be going mad, but autocomplete doesn't seem to be working in v4.43.06
I have a premium licence and the queries are executing ok, but the autocomplete on parameters isn't working e.g.
from b in this.BusinessUnits where b.Initially I was using DbContext, but recently have been using LINQ to SQL, so it's possible that I've simply (gone mad) forgotten how to use DbContext properly in LinqPad.
But I'm pretty sure it previously autocompleted on pressing "." after b
I've tried using the short cut keys listed under Edit > Autocompletion to no avail.
Any ideas?
Comments
I have recently installed VS2012 and .net 4.5 but I can't imagine it's that.
I'll try isolate the problem.
It's working ok in Linq to SQL, just not in DBContext v4.3 (so far that's all I've tried).
I've been in the wonderful world of LinqPad + Linq to SQL, I completely forgot what I needed to do to get my EF projects to run.
My EF projects have the DbContext in one dll and Entities in another. I cleaned up my default assembly references some time ago and completely forgot to re-add the namespace / assembly references when working with my EF projects! My bad.
Funny how it still works, guessing my DbContext class has enough information locked in it's dll that it doesn't actually need the Entity dll's to run per-say.
Problem solved, if anyone like me needs some more sleep.
I noticed that linqpad is displaying the right type in the tool tip while mousing over but F1 does not bring up the help and the Help menu does not pop up the help.
Any ideas what could cause this?
The answer above did not help.
I also tried Version: 4.42.1.0
Its almost like the auto complete doesn't know what DBSets are or something. The compiler does because the queries run fine and I get the correct results or error messages if I fat finger something.
Adding EntityFramework using nuget in the F4 interface did not fix it. Only that specific dll did. Questing is why did I not have to do that on all my computers? Also what EntityFramework reference does Linqpad use by default?