Scott Herold is happy to announce the release of the vEcoShell 1.2.6. It’s out of beta and officially has been deemed as a stable release. The list of features is quite limited, but the biggest change is multi session management which makes copying and pasting from the web and PS1 files possible. Under the hood every single script in the function library was re-written from scratch. Scott also has transferred the community homepage of The vEcoShell Initiative to Vizioncore’s vCommunity. 
What's New with 1.2.6?
•Completely rewritten PowerPack to support VMware PowerCLU 4.0 Update 1 and its ability to manage connections to multiple $viServer objects.
•Ability to copy and paste code from "PowerShell Code" tab directly into standalone PS1 files (Will still need to Add-PSSnapin and Connect-VIServer for script to function).
•Ability to copy and paste code snippets from the internet and they will work without needing to add the $managedHost.connection code everywhere.
Download the latest version of vEcoShell and additional PowerPacks here.
Scott Herold about the GA: I am happy to announce that the 1.2.6 version of vEcoShell is now available on the Downloads Page. This update brings us into full compatibility with VMware PowerCLI 4.0 U1. In addition, we have decided to remove the product from beta and have provided our first stable release , which has been rigourously tested by the Vizioncore QC team. vEcoShell will remain Freeware, and continue to have a community support policy. The major difference in 1.2.6 is in how connections to multiple vCenter or ESX Servers are managed. In previous versions, vEcoShell maintained all session management and required custom code in nearly all of it's scripts to function properly. These scripts could not run externally to vEcoShell, so the PowerShell Code tab provided limited value. With the 1.2.6 release, vEcoShell now lets PowerCLI manage all connections. This means we were able to remove all custom code from our script library. Nearly every script that is in vEcoShell today can be run externally. Simply copy a code block from the "PowerShell Code"...