Adding my own 2¢ to the PowerShell & Technology Communities
Building a PowerShell module should not be too hard. In fact, on the surface it’s pretty simple. Collect a bunch of functions, classes, enumerations, (whatever else you want), bundle them together and provide a wrapper in the form of a PSD1/PSM file. Building a module should be straightforward – and it is – except when you make dumb mistakes. Don’t make my mistakes.
I’m trying to get better about using the new versions of PowerShell (7.x) instead of Windows PowerShell (5.x), but I find that I forget to install it on some machines. To make that easier, I wrote myself a script (in PowerShell) to install PowerShell. I know – don’t judge me. This is the script. Sadly, … Read more
Building a PowerShell Module from scratch is a daunting task, but I’ll try to describe how I started this as a solo endeavor.
Just stashing this here in prep for a larger article. As written the above will install the utilities in C:\UTILS. However, some workstations may block these types of installs. In that event, I’ve added a flag ($IsMachine) which can be flipped to False and install in the current user’s profile.
I just needed a place to stash this and my GitHub didn’t seem appropriate. I make no guarantees that this will work and it’s only been tested on one system so far. I added the -Unique flag to the end of the download URL detection as indicated in a below message. (Again, nice catch!)
In learning about PowerShell and Web API’s, I figured I would start with something fun and easy.
Let’s forget all about my previous step 3. For the sake of argument, step 3 is dead, long live step 3.1! Any script should be a living, breathing document which gets updated as needed. In this case, it was needed. Why would I burn such a good script to the ground? Well, to be blunt, I’ve found a better way to do this, with better ultimate performance.
If you need a refresher on the previous steps, I have Step 1 for Hyper-V, Step 1 for VMware, and Step 2.
In Part 1 of trying to tame my photos, I tried to wrangle my horribly organized photo library. My organization skills were lacking, like many, when it comes to photos. We take them, we import them or save them and then we… forget about them. That’s a problem when I’m trying to handle large amounts of them (22.8 GB in 13,316 files) and organize them in ways that seem sensible. To use this we leverage the metadata tags that describe the date and time the photo was taken.
No one could ever accuse me of being a shutterbug. I’m more of a casual photographer and much most of that was from mobile devices. But that’s not the be-all-end-all. I’ve also got scores of scans of old photographs, screenshots, and a bunch of other graphics that have accumulated over the years. Thankfully modern mobile devices tag photos with a plethora of information. Now it’s just a matter of getting to that information. These tags can help you organize your data so you don’t run into my problems.