The post below explains some tools which are quite handy when debuggin LINQ to Entity statements, but I have used DBContext instead of ObjectContext connection
http://blog.falafel.com/debugging-in-linq-hell/
Also, to make internal classes visible to Linq Pad use an assembly attribute.
http://stackoverflow.com/questions/14354157/make-internal-classes-visible-to-others-assemblies
but if they are signed, this won't work
http://forum.linqpad.net/discussion/747/internalsvisibleto-on-datacontext-in-signed-assembly
Also, there is an extention in visual studio to connect to linqpad
https://github.com/nbasakuragi/LINQBridgeVs
http://blog.falafel.com/debugging-in-linq-hell/
Also, to make internal classes visible to Linq Pad use an assembly attribute.
[assembly: InternalsVisibleTo("LINQPadQuery")]
http://stackoverflow.com/questions/14354157/make-internal-classes-visible-to-others-assemblies
but if they are signed, this won't work
http://forum.linqpad.net/discussion/747/internalsvisibleto-on-datacontext-in-signed-assembly
Also, there is an extention in visual studio to connect to linqpad
https://github.com/nbasakuragi/LINQBridgeVs
No comments:
Post a Comment