From the course: .NET Essentials: Working with LINQ

Why use LINQPad?

- I'm a long time Visual Studio user. It's been my primary IDE for 20 years. And yet, for most of the examples in this course, I will use an editor called LINQPad. It's a versatile and valuable Scratchpad. I always install LINQPad on my dev computer. Let's see what offers over a Visual Studio. As the name suggests, LINQPad was created as a lightweight tool to write, test, and debug LINQ queries. Because LINQPad is easy to use, there is no need to build a throwaway Visual Studio project, or clutter an existing project with experimental quarries. Instead, use LINQPad to investigate LINQ in a purpose built application. Over the years, LINQPad has grown. It's not restricted to just LINQ code. I use LINQPad to write fast snippets of code, which I can test interactively many times faster than in Visual Studio. You get the same IntelliSense and autocomplete as in visual studio, there is also a step by step debugger. So the experience is close to what you get in the Visual Studio IDE. In addition, it supports connections to databases and other sources. Once you connect and authenticate, you can run SQL and LINQ queries against the database. This means you don't have to mess with the SQL management studio or use the Visual Studio data windows. To conclude, LIQPad is a nice way to write and test code. Better than most Ripple tools I've used. Think of it as an interactive Scratchpad for.NET code.

Contents