YOW! 2011: Joe Albahari - LINQ, LINQPad, and .NET Async (and a little Rx, too)

Sign in to queue

The Discussion

  • User profile image
    mattjcowan

    I use LINQPad for so many things, it's easy to forget how valuable it really is. It's like a writer's favorite text editor, only for a C# developer. I don't know what I'd do without it Smiley . From debugging, optimizing, and creating nice database queries, to writing 100s of plain C# management scripts to administer SharePoint farms. Not sure what I'd do without it. Agreed! Thanks for this awesome little (big) tool. 

  • User profile image
    Ian2

    Hands up, I havn't been using LinqPad but it looks interesting!  My first thought was to use it in an existing project where I am looking at querying RSS style feeds.  Is there an existing generic style XML driver (or an RSS specific one?) or do I need to be looking at creating one for LinqPad?  With apologies if this is a bit of a "noob" question.

    OK, I get it now (slaps hand on forehead)

  • User profile image
    Libra Thinker

    Cool!

  • User profile image
    exoteric

    LINQPad and Joe rocks. Bought an autocomplete license for work. Smiley
    Watching... 

  • User profile image
    vesuvius

    .NET has some pretty amazing projects, with LINQPad being a project  "that goes to eleven"

  • User profile image
    Richard.Hein

    It's great to hear from Joseph ... LINQPad is one of my favorite tools, and the premium version is well worth it.  I use it as much as I use Visual Studio for all those things that VS is too heavyweight for.  I write a function and test it in LINQPad before I consider adding it to a project some place in VS.  It's like a brainstorming tool, because it just takes so much less time to use than VS.  So, I hope that it stays light weight and responsive and it sounds like it will as new features rely on asynchrony features of C# 5. 

    Roslyn will certainly be a game changer for this kind of application.  I was wondering if and when you'd ask about that Charles ... you left it until the end, and I was biting my tongue the whole time waiting to post, "why didn't you ask about Roslyn?".  Wink  Joseph did mention that it will make things simpler for him, but it will afford more opportunity for competitors to develop IDEs.

     

     

     

     

  • User profile image
    brianbec

    One of my colleagues said "With ordinary tools, you code and then test; with LinqPad, you test and then code."  Use it in concert with the Visual-Studio Unit Test Framework (VSUTF) and you will be writing bulletproof code with unbelievable speed. 

    Technique: get your code working in LinqPad where the code-test-look cycle is fast and frictionless (LinqPad's Dump() + the charting tools in System.Windows.Forms.DataVisualization + plus the Sho-viz libraries are worth their weight in diamonds for code-test-look speed!). Copy all your test stuff into VSUTF and the target code into your VS projects and BAKE 'EM.  Really great!

  • User profile image
    exoteric

    Quite. It is so much faster to prototype and test in LinqPad. I wish I'd started with this approach to begin with.

    I do miss NuGet integration though. It would be much easier to quickly toss together some new script using existing open-source libraries. It just has to be done in the usual light-weight LinqPad way.

  • User profile image
    brianbec

    @exoteric:Even without NuGet, it still pays off bigtime.  I have some LinqPad scripts where i have integrated OpenCv (via PInvoke), QuickGraph (see codeplex), the SQL server Geomety and Geography data types, LINQ / Objects, LINQ / XML, LINQ / Rx, Task lib, all in a single script (not just to use them for sophomoric show-off fun, but because they were the most economical way to get the job done!).  I took the effort to pull this all into Visual Studio (not really hard, mostly just rationalizing the namespaces), and by gum it all just works. <3 + + + +

Add Your 2 Cents