portresponse.blogg.se - Code scratchpad

#Code scratchpad drivers#
#Code scratchpad code#

When examining the query results there might be a need to explore the related entities. Most SQL IDEs offer at least some sort of intellisense, but it pales in comparison to the linqpad one. Querying using LINQ is not only more convenient but also almost friction-free because of a rock-solid intellisense thanks to the typed data context. By using linqpad you can avoid touching Oracle SQL altogether.). For me, it’s a life saver when I’m forced to work with oracle databases (Oracle SQL has a very specific syntax and most of MSSQL/MySQL developers find it quite irritating. This makes linqpad a mighty tool when working with a database with an unfamiliar query syntax.

#Code scratchpad drivers#

There are a myriad of other officially supported DB drivers (Oracle, PostgreSQL, mysql, MariaDB, Azure table storage, MongoDB, SAP HANA, and more). Another option is to load a typed Entity Framework DataContext from an existing dll. This context is then used for querying of the database in the same manner as it would be used in any. Based on the connection, a LinqToSql DB context is generated. Typical DB workflow with linqpad starts with adding a new DB connection. It’s as simple as this:ĭata.csv > lprun myquery.linq CustomArg1 CustomArg2 > output.txt Data analytics with linqpad The file can then be run via linqpad or as a process in your favorite shell via the lprun command (you can access STDIN, STDOUT, and command arguments in your linqpad script the same way you would in a typical. linq file and share it with your colleagues.

#Code scratchpad code#

Once your idea becomes polished enough, you can simply copy-paste the code into your existing project in your main IDE (e.g. Visual Studio or Rider) or save it to a. NET ecosystem and integrated VS-style debugger (that one is available only in the paid version though). Linqpad also comes with a built-in nuget package manager to leverage any package from the amazing.

Other methods, classes, structs, and records can be defined in the script in this mode.

The script will contain a Main() method serving as an entry point (think of this mode as a Program.cs class equivalent.).

Dump() has to be called explicitly to display expression result.

The script can contain multiple expressions.

Great for quick DB queries, generating guids, and other single line shenanigans.

No need to add at the end and Dump() is called automatically on the expression result.

The script can contain only a single expression.

Once you start using linqpad, gone are the days when you had to tediously set up yet another console project when you wanted to quickly whip up a simple CLI-based tool (yes, since C# 9 you can use Top-level statements for the same reason, but it lacks many of the possibilities offered by linqpad).ĭepending on the desired use case, linqpad script can be run in three different modes:

There are two main ways to leverage linqpad for more productivity: 1) scripting in your favorite language (C#/F#/VB.NET) and 2) easy database querying, edits, and data analytics. It can also render bitmaps, xml data, and even WPF and WinForms controls! Boosting your productivity game with linqpad It will analyze the object graph and use its fine-tuned heuristics to present the object’s data in the most efficient way possible.

The single most powerful feature of linqpad is the Dump() extension method that you can call on any object.

But there is also a benefit in keeping a virtual scratchpad as well – and linqpad is just the right tool for the job. Many engineers keep a paper scratchpad on their desk to doodle ideas and concepts that can eventually be turned into a working piece of technology.