database-tools

Out-GridView always produces a table with one object per line: Get-Process -Id $pid | Out-GridView Occasionally, it would be more helpful to display...

If you’d like to format information to given culture standards, this is really simple by using ToString() and the appropriate target...

Let’s assume you received data like numbers or date as text. Whenever information is reduced to text, you are challenged with culture-specific...

There are many different ways how objects can be transformed into text. In case you sometimes get confused, here is a quick refresher. Take a look:...

Execution policy can prevent scripts from running. It is designed to be a user preference setting, so you should always be able to change the...

In a previous example we used HashSets to compare numeric lists, and find out which elements were found in both list, or in just one list. The same...

Often a script needs to find out whether two lists are the same, or which elements are missing from a list. Instead of investing much programming...

Occasionally you see scripts that use Select-Object to append information to existing objects. This can look similar to the code below: Get-Process...

In the previous tip we looked at command extensions for the good old PowerShell ISE. Here is another sample that adds the CTRL+K keyboard shortcut...

The good old PowerShell ISE exposes some expandability connectors. If you’d like to toggle comments in selected text by pressing CTRL+K, for...

In previous scripts we worked a lot with hash tables, and even loaded them from .psd1 files. If you need the data in a different format, for example...

In a previous tip we introduced Import-LocalizedData to read in data stored in a .psd1 file. Starting in PowerShell 5, there is a new cmdlet named...

There are many ways how a script can store data information. One is especially convenient. Here is the code: Import-LocalizedData -BaseDirectory...

PowerShell can use .NET type names, for example to convert values to a given type. Frequently, scripts use a variety of formats to define .NET...

Error handling does not necessarily have to be complex. It can be as simple as checking whether the last command executed successfully: # suppress...