Welcome to the LINQPad forum!

edited May 2013
This forum is for general LINQPad discussions (topics that are not a good fit for StackOverflow or UserVoice).


  • Hi Joe,
    Great to see the LINQPad forum stand on its own now! Keep up the good work!
    - Arno Tolmeijer
  • Hi Joe,
    I've been using LinqPad for about a year. A couple of months ago I added Intellisense.

    I just wanted to let you know that I think that LinqPad is a great product.

    Have a good weekend.
  • Thanks for supporting LINQPad!
  • Hi Joe,
    I have been using LINQPad every day for one week know. It is already one of those few tools I fire up in the morning and close it only when I leave the office in the evening.

    I am using LINQPad for
    1) automating Excel with C#
    2) learning C# and LINQ
    3) copying and moving files between different servers
    4) the development of a simple IronPython console within LINQPad

  • Joe,

    Thanks for making my job so much easier. Arguably the best invention since toilet paper :>)
  • LinqPad is the bomb. Not only in helping me learn, debug, and optimize my Linq but also as a c# scripting tool. Testing functions and writing quick utilities to fix things on my PC or in a database take so much less time then having to create a whole program to do the same because T-SQL isn't powerful enough. Such a time saver.
  • I am a huge fan of LINQPad, been so for years- however this is the first time I signed up for a forum account. The password requirments are a little too strong I think.
  • LinqPad is still something new for me. Even Linq is. But with this excelent tool i started to query the DB using Linq and the process of learning it is being very fun. Also, linqpad provides me a scratch board, easy to use and test some dirty code. Keep up the powerfull work.
  • I've been using LINQPad, including LINQPad Pro, for at least five years now. In my little corner of the coding world, it long ago supplanted an outstanding predecessor, Snippet Compiler, which was the "go-to" app for working out small (and sometimes not-so-small) pieces of .NET code in the years before .NET 3.5. As with its predecessor, I've spent many hours with LINQPad--perhaps even as much time as in Visual Studio!--working out problems, learning the .NET Framework (including LINQ, of course), learning APIs and libraries (especially thanks to LINQPad's outstanding support for NuGet) and writing utilities that are much easier to implement in C# or F# than in a scripting language.

    You wanna know about some killer capabilities in LINQPad? How about that time--or, really, those times--when I've needed to parse or build LINQ expressions? LINQPad has made it easy for me to inspect the structure and properties of expressions, allowing me to build and troubleshoot my code much more quickly and efficiently than if I had to rely on the Visual Studio IDE. Or what about those times when I've wanted to see the IL code that a short snippet generates? Rather than having to go through a laborious process of building an assembly, locating it in the file system, and firing up ILDasm, LINQPad allows me to type the snippet, run it, and view the IL without ever having to leave the app? And then there are the times when I've needed to manipulate my iTunes music collection...

    In short, LINQPad provides almost everything you need for working out the building blocks of your code without burdening you with the ceremony of a full-blown IDE. It's where I go to think small now so that I can think big later.
  • I use LinqPad every single day at work. Need to generate a report? Need to modify a database? Need to upload a csv file? Need to test a small piece of code, to see if it does what is expected? Visual Studio is great for handling big projects, but is horrible to use when you need to try something, make something small, or do something you plan on only using once. With LinqPad, I can just open it up, and start programming, without worrying about cluttering up my projects folder. I also find that because my LinqPad scripts generally only do one task, it's very easy to copy, and reuse them for similar tasks.
  • LinqPad is a great tool. I allways use it when I develop in a big Visual Studio multi-project environment. You can make quick tests, try out new technics/technologies, for performance tests, and of course to show new opportunities to our collegues.
    With Linq scripts yoy can focus on your idea, you can keep everything clear, without any disturbing complexities.
    Thanxs for this product, keep on developing. (and happy new year!)
This discussion has been closed.