LinQ – holy crap balls

holy crap-balls! as my friend jason beaudreau would say...If you have not checked out LinQ, please do, in fact do nothing else but go and learn this. as a meta-data guy, this extension of C# has unreal potential. having the ability to do impact analysis across the data layer, object layer and event data is fast becoming a reality. not that it wasn’t there before, this just simplifies the development of these types of solutions. imagine a visualization debugger, that also shows upstream and downstream impacts in real-time. HUH?

Read about it hear...


Install it from here...

Comments (2)

  1. Bob T says:

    years later as hind sight is 20/20

    After reading the the complex script to create a dynamic query using LinQ I hope the drop it.

    Lamda/LinQ types like VAR that are as obtuse as they are meaningless.

    : Func<int,int,int> func = (int a, int b) => a + b;

    2: Expression<Func<int,int,int>> expr = (int a, int b) => a + b;

    Obviously the following code looks very confusing:

    : public static class Linq {

    2:   // Returns the given anonymous method as a lambda expression

    3:   public static Expression<Func<T, R>>

    4:       Expr<T, R>(Expression<Func<T, R>> f) {

    5:     return f;

    6:   }


    8:   // Returns the given anonymous function as a Func delegate

    9:   public static Func<T, R>

    10:       Func<T, R>(Func<T, R> f) {

    11:     return f;

    12:   }

    13: }

    Obviously the following code looks very confusing:  

    Yeah no kidding.

  2. My knee-jerk reaction:

    With the inclusion of the ability to write stored procedures in C#, this appears to just further muddy the waters about where business logic should be written.

Skip to main content