Let’s start over…

Many times over I thought about what I should be blogging about.

PowerShell’s the future and I really like everything PowerShell related, so a theme for the blog was ‘easy’.
However I’m not really a front runner when it comes to IT, so most of the things I’d be playing with have been done before.

I’d get stuck on what to write about, because surely no one would be interested in ‘another basic PowerShell blog’.
Writing doesn’t come naturally to me and English is not my native language, so transferring thoughts to a blog post can be challenging.
Besides that I normally overthink whatever I write, causing a ‘simple’ blog post to take me hours if not days.

What changed?

In 2018 I had a few breakthroughs that jump-started my love for PowerShell again:

All in all, I’m coding more and more again, finding new reasons to look into it and wanting to share my findings with others.

What does this mean for the blog?

Well, besides an updated colour scheme and logo, I want to grow through teaching more and attending/speaking at more seminars.

But I won’t just blog about PowerShell anymore.
I’ll try and write more about various things, such as other technologies I’m playing with [PowerShell related or not], share interesting articles/tweets that I’ve read.

This should mean some posts will be shorter than ‘normal’, but I’m hoping that like with coding,  writing more will help me become a better writer.
Possibly it will even help me create content more easily.

All in all, let’s start writing again 🙂


DuPSUG Basics – Deux

Today was another great day with other PowerShell enthousiasts where I got to share some tricks of the trade.

During DuPSUG’s second Basics event, I was once again able to provide a session, this time about “Improving your Scripts”.

I had a blast and I hope others did too and as promised I’ve made my code available on GitHub on the general DuPSUG GitHub.


I’d like to thank all the people attending today’s session for your time and patience, all other speakers for sharing their time, code and tricks and of course @EJHeeres for arranging the event perfectly.

Hope to see you again soon and happy scripting! 🙂


Using Visual Studio Code for PowerShell – Settings

Like many others, I’m giving Microsoft’s free code editor Visual Studio Code a try.

Perhaps a bit late to the party, I know, but I’ve been a big fan of Microsoft’s built in PowerShell ISE editor, especially when combined with Dr. Tobias Weltner’s ISESteroids.

So what’s this post about?

Nothing special for now, just wanted to share my default Visual Studio Code settings.json file [Ctrl + , ].

This file sets your personal preferences within the editor, making the look and feel just a bit smoother to my liking.
Especially when you’re used to one specific editor, switching to another one might not be as easy as you’d like.

With small setting changes, you can perhaps ease that change..

Some explanation might be handy 🙂

As you might have noticed, I write mainly about PowerShell items, so my focus on the settings are mainly for the PowerShell experience.

PowerShell first

I’ve configured VSCode to automatically set the language to PowerShell using:

Do note that the language bit is case sensitive and PowerShell, Powershell or any other variation will not work. Lowercase all the way on the language.
This bit saves you from having to define each new file as language PowerShell [Ctrl + K -> M -> ps ]

Of course you also want PowerShell to automatically load on start, making the experience better and quicker to my liking and enabling the default PowerShell application as the integrated shell.

Formatting preferences

Now there are also a few things that work together:

The first 2 are ways that work for me, trimming white spaces at the end of lines and formatting open braces [ { & } ] in a particular way.

The second 2 lines forces VSCode to apply them immediately when you type, instead of having to apply the formatting rules [Shift + Alt + F].

Last but not least

A golden setting for me:

While using VSCode, I noticed this annoying behaviour when just running a small bit of code and executing it through the F8 key…
After executing the code, it would automatically set the focus on the Console section [lower part] instead of the Editor section. If you’d want to do something, you would have to manually select the Editor section again before you can continue.

This little piece of code saves you from that hassle.

Full file


Now I know for some people it’s nothing special, but for me these small settings make a huge difference in my usage experience for Visual Studio Code.

Perhaps you have some other settings you’d like to share, feel free to comment!

Happy scripting! 🙂