I’ve had an disagreement recently with a colleague about the usage of open-source automation tools, especially Chocolatey in Business environments. A key point of this argument was the integration of new open source tools into long-existing, mostly commercial software based workflows.
One of the main reasons to use Chocolatey in an organization is its ability to integrate seamlessly with already existing automation infrastructure.
Getting PowerShell Core to run on Linux was easy enough. As I’m running Kubuntu 18.10 it’s a simple case of using snapd.
However, I didn’t expect running PowerShell Core on Linux to be problem free. And it wasn’t. After installing my own PsTodoTxt module from the PowerShell Gallery, PowerShell couldn’t find it.
I started using PC’s with MS Dos 4 and then 5. I graduated to Windows 3.11 and I’ve used every single version of Windows released since then. I lasted two months on Vista which some have claimed I should get a medal for (Vista wasn’t all that bad…).
But I’ve also dabbled outside of the Windows world. I used OS/2 Warp for almost a year in 1995 (I still have the box!
As I mentioned in my last post, I will be giving my Git Fundamentals - Open up a world of community and collaboration three times this month and now we are ready for time number two!
Come along to the DevOps North East User Group to hear myself and Craig Porteous[t|b] talk about The PowerShell Standards Agency and, as I said, my talk on Git Fundamentals - Open up a world of community and collaboration.
It’s been a while since I’ve posted. Work. Life. And speaking. Have all taken it’s toll on my time. It’s always at the back of my mind when I come across a problem, solve it and think ‘hey that would make a good blog post’. And then promptly get wrapped up in something else and that solution never gets shared.
… but that does lead me nicely to my next big knowledge sharing event (it’s like I planned this post!
In my move away from VMware workstation I’ve been using Hyper-V more and more for virtual machines but I’ve come across a problem only recently. DNS resolution and internet browsing is noticeably slower with many pages not being able to be viewed at all. So after much frustration I decided to tackle this problem today and I found something unexpected.
Along with the new Fall Creators Update released at the tail end of 2017 is a new Hyper-V NAT switch called Hyper-V (Default Switch).
The month long celebration of open source gives you a chance to brush up on your git, help open source projects and get yourself some stickers or a t-shirt!
I’ve been resisting buying a Stream Deck for a while now but finally succumbed to temptation and it arrived today. Setting it up is fairly easy but associating a program with a button does not extract the icon from the executable. So I looked for a way to extract the icon myself. And of course I looked to use PowerShell.
I knew there was a Drawing namespace in .NET so I browsed the latest .
In a previous blog post I talked about working with enums in PowerShell and how useful they are. Would they not be even more useful if we could create and use our own enums? Yes, yes they would. And if you read below you’ll find out how.
You’ve been able to create enums in PowerShell since v1.0. But since the introduction of PowerShell version 5 there are now two ways:
