LINQPad for writing C# snippets

by Dec 20, 2022

Sometimes I want to write a small C# snippet to test or check an idea.

But it is too much effort to start up Visual Studio (Code) or Rider and create a console app.

Even when I have any of these editors open, it is still much of a hassle. It’s often not even worth writing a test case for it.

LINQPad is an ancient tool, originally created to quickly write LINQ queries, but it is also perfect to write dotnet code (C#/F#/VB).

It’s my go to tool for writing C# snippets and just run them.

It’s eliminating friction for me, so I bought the tool. Buying gives, me intellisense (and debugging). You only realize how dependent you are on intellisense when you don’t have it 🤣.

What’s your favorite tool that solves a tiny problem?

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more