We have changed the way we are delivering PWPS_DAB down to the users in an effort to help get you the latest updates the fastest way possible. PWPS_DAB will now be available in the PowerShell Gallery. PowerShell Gallery is a repository in the cloud that you can pull PowerShell modules down directly into PowerShell and/or upgrade the version you have. If you go to www.powershellgallery.com and search for PWPS_DAB you will see the installs. To update your local copy:
To get a new version once it is installed just type "Update-Module pwps_dab -Verbose"
A lot of us here are actually using a two step process of "Uninstall-Module pwps_dab -Verbose" and "Install-Module pwps_dab -Verbose" for a completely clean install, but that is completely up to you. Personally I have created a script (update.ps1) which has the Uninstall-Module and Install-Module inside of it and when i need to update i just run that script.
So basically this means no more downloading MSIs, etc., etc. Hope you find this useful and please let us know if it works out for you.
One more note on this. If you've been doing:
Import-Module -Name "C:\Program Files (x86)\Bentley\ProjectWise\bin\PowerShell\pwps\PWPS.dll" -Verbose
Import-Module -Name "C:\Program Files (x86)\Bentley\ProjectWise\bin\PowerShell\pwps\PWPS_DAB.dll" -Verbose
Your scripts will fail after updating to 126.96.36.199 from PSGallery. The path is changed. I'd recommend not specifying the path at all. I use:
Import-Module -Name PWPS
Import-Module -Name PWPS_DAB -DisableNameChecking
the -DisableNameChecking turns off the warning messages about the unapproved verbs used in some of the pwps_dab commands (Undo-PWLogin i believe is one that is triggering this)
Actually, I think CheckIn-PWDocumentOrFree and CheckOut-PWDocument are what PowerShell complains about. With a little thought, I can usually figure out a PowerShell-approved "verb" to use in our cmdlet names, but those two are so DMS-centric that I couldn't come up with a logical synonym.