Ensuring your organization is secure has to start someplace. For most administrators this is a daunting task. Where do I start? What do I secure first? What would a Threat Actor look for? The sheer number of configuration capabilities in Windows Server and Windows 10 can make these questions hard to answer.
So, you want to play with that shiny new ReST API you’ve discovered but in doing research on consuming ReST APIs with PowerShell you’ve discovered two different cmdlets Which one do I use? Which one is best? These are the same questions I had about 8 months ago.
Welcome to the third and final C# to PowerShell article. These articles aren’t meant as full tutorials, merely a peek in to some of the changes you will experience moving from C# to PowerShell . I saved the best for last I promise you.
Welcome to Part 2 of my C# to PowerShell series where I talk about interesting things I’ve learned on my path from C# to PowerShell. This article will focus on Casing, Error Handling and some of the minor oddities that PowerShell has.
I lost the better part of an entire workday trying to figure out how to run
docker-compose up on my RancherOS box. I found alot of other people asking the same question but nobody provided a clear cut answer.
I, like most C# developers, had heard about PowerShell since it came out. I originally shunned PowerShell as ‘just a scripting language’ and assumed it could never do what I could do with a custom C# tool. Over the past year I have learned how very wrong I was. In this article I will try to highlight some information about PowerShell I found useful during my transition.