@vmiss33 Regarding the versioning mystery of PowerCLI in your blog post... There were 3 main reasons that I chose to go with 10.0...
1. We needed to diverge from vSphere versioning, as there were far too many instances where people thought they had to run the same version of PowerCLI as vSphere. Additionally, we wanted to move to semantic versioning, and version each module separately on powershell gallery.
2. With 10.0 we introduced support for PowerShell Core, which was a big deal, as you mentioned in your blog post. We had to make it a major version number change, but we knew vSphere 7 would come out soon and that would just continue the confusion around version compatability.
3. the version '10.0.0' has significance because it felt like we were starting a new era, it was a departure from the vSphere versioning scheme, and we were celebrating the 10th anniversary of the existence of PowerCLI. (Formerly known as VI Toolkit, way back in the day).
So there ya have it. The story straight from the human that made that decision! :)
You can follow @jakerobinson.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:
Those who think consciousness raising & movement building are disconnected, or even a distraction from electoral politics have not paid attention to the history of social change.In this thread, we
Read more
The 2020s will be known as the Remote Work decadeA few predictions of what is likely to emerge[ a thread ] Third Space: Office and Working from Home will
Read more
1/29: Have you ever had a concept explained to you that helps frame complex issues you’ve been wrestling with and opens your eyes to new possibilities? A concept that I
Read more
By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.