.debug

News flash: I still hate LINQ.

Rant #1: “LINQ Method cannot be translated into a store expression.”

As always, Microsoft and their cryptic error messages.  I ran across this error while developing a Worker Role Azure application that heavily relies on LINQ to Entities.  The experience is somewhat akin to this, but it was a bit more rude awakening experience for me.  I kinda know why this doesn’t work now, but my beef with this is that why isn’t it flagged as a COMPILER error?  Why is it a run-time error?

Rant #2: Why do I have to explicitly have to call .Detach() to an Entity when the EntityConnection and context is already out of scope?  I mean, WTF is that?  And why oh why do I have to explicitly call .Attach() to a new EntityConnection and context?  Shouldn’t it automagically work?!

Now, I know LINQ to Entity is still basically in its infancy, and I’m sure by .NET v27.5 or whatever, Microsoft may have even perfected it.  That’s assuming they don’t introduce another programming paradigm into their Framework.

Sometimes, I wonder WHY Microsoft had to tack on the LINQ stuff to existing C# or VB or whatever.  Wouldn’t it make more sense to define a new language altogether?  Calling delegates/methods/functions across multiple languages is dead easy anyway.

I still don’t see the value of LINQ at all…the only somewhat cool use of the extension is the ability to filter contents an IEnumerable object.  THAT’S ABOUT IT.  Database access?  I still prefer ADO.NET.  XML?  XSLT and XPath is enough for that.