It's not a joke. Just 2 real bugs:
1) Too many "nots". It should read "Can not transform LINQ". We'll change that text. This error is rare, guess that's why we didn't notice.
2) The error appears if something goes wrong internally when analyzing a LINQ expression. To fix that we'll need to see the LINQ expression where it's shown. Please send it in a ticket or use JC's "Report good-code-red" quick-fix, which will also send the code to us. Thanks for your help!
Dennis :: Dr. Code
the Telerik team
Sharpen your .NET Ninja skills
! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>