Trouble with 3.0.0-beta5

I have downloaded the 3.0.0-beta3 and I am missing some important cmdlets. Then looking at “Package Details” in the PowerShell gallery, there are tags and functions but the cmdlet section is missing completely. I realized this when looking for ‘Get-UDDashboard’ which is available in beta2 but no longer in beta5.

We won’t be releasing UD as a PowerShell module any more. It’s now part of PowerShell Universal. I haven’t figured out exactly what to do with the existing PS module on the Gallery.

If you want to see how to migrate to PSU from UD, check out this doc:

Thanks @adam, I will have a look at it.

@adam, I am trying to get familiar with dashboards in PowerShell Universal now. In some posts the cmdlet Connect-UDDashboard is mentioned but I cannot find it. I cannot find something to stop or remove UDDashboards.

How can I get the same flow for developing and testing a dashboard like in UD?

$port = 88
$fqdn = [System.Net.Dns]::Resolve($env:COMPUTERNAME).HostName
Get-UDDashboard | Where-Object Port -eq $port | Stop-UDDashboard

$dashboard = New-UDDashboard -Title Test -Content {

Start-UDDashboard -Port $port -Dashboard $MyDashboard

& 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe' -ArgumentList "http://$($fqdn):$port"

Seems that using the web API is the only way at the moment. Not as nice as having cmdlets for these tasks but it works.

I would recommend using the VS Code extension. It will automatically import the PowerShell modules and allow you to easily access the Universal config files. I spent some time writing up a docs page about this because I figure other people have the same question: