Anybody tested PWPS and PWPS_DAB modules with Powershell Core 6?
We've tested it and its working if you are just creating new items, the only issue we have is that the cmdlets do not autoload when Powershell 7 opens. You can either put this in every script
[System.Reflection.Assembly]::LoadFrom("C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Windows.Forms.dll") Import-Module -Name "PWPS_DAB" -DisableNameChecking -UseWindowsPowershellor you can put it in your Powershell Profile to load it each time PS7 is opened.I have not been able to get the -SkipEditionCheck to work. Also working with object types is an issue as PS7 deserialized objects.+1 for PS7 support, we use it to tie .net Core Forms into PW and the new .net core requires PS7 to function properly.
thanks, that's good info. I've been thinking about putting PowerShell 7 on one of my boxes. If I understand correctly if you install PowerShell 7 you can still load PowerShell 5 which has full compatibility still, you just can't use any powershell 7 features with it.
Be nice if there was a way of blocking the need for the Windows Forms unless explicitly needed for a particular command.
So ive got a bit deeper with this.. Basically any projectwise items that come in get desearlized i think is the correct term. The web developers tell me they cant use Powershell 5...i have my doubts.. but what I've done to get around this for now is that any interaction that manipulates an already existing ProjectWise object. I start up a new shell of PS5 and send it the script i need it to run. $Session = New-PSSession -ComputerName $Name Invoke-Command -Session $Session -ArgumentList $DocLoc,$DocName -ScriptBlock $Command