http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660The IL munging only needs to be done once if it is done well. http://ayende.com/2046/is-linq-for-mortals#comment5http://ayende.com/2046/is-linq-for-mortals#comment5Fri, 16 Feb 2007 21:02:12 GMTYes, I know how it is translated, it is just that this is getting scary. IL Munging is not for the faint of heart, and getting it wrong can be very confusing. I wonder what the debugger guys are working on now. http://ayende.com/2046/is-linq-for-mortals#comment4http://ayende.com/2046/is-linq-for-mortals#comment4Fri, 16 Feb 2007 20:21:51 GMT@Ayende, Perhaps one could do some IL munging to get the results set after each extension method call? I assume you are familiar with how LINQ syntactic sugar gets converted to a string of method calls? http://ayende.com/2046/is-linq-for-mortals#comment3http://ayende.com/2046/is-linq-for-mortals#comment3Fri, 16 Feb 2007 20:00:14 GMTNot easily, no. You would need to import all the referenced assemblies, etc. It is possible, just not trivial. Most so because often enough what would happen is the query won't run in memory but translated to some other form (SQL, XPath), which may cause wildly different results http://ayende.com/2046/is-linq-for-mortals#comment2http://ayende.com/2046/is-linq-for-mortals#comment2Sat, 03 Feb 2007 21:30:52 GMT@ayende re luke a linq query analyzer with F5 simplicity to make the cycle similarly quick, seems feasible though - doesn't it? (real question, I'm probably forgetting something) http://ayende.com/2046/is-linq-for-mortals#comment1http://ayende.com/2046/is-linq-for-mortals#comment1Sat, 03 Feb 2007 21:01:34 GMT