Aliases?

[spencermathews]

What's up with all the aliases in the setup wizard?

They don't seem to make their way into the config files and don't persist past the current session. Given this, and the fact that they don't appear to be mentioned anywhere in the docs, there inclusion in the setup wizard is quite puzzling. What purpose do they serve? For the sanity of newcomers, why not just omit them from the wizard, or wrap all "Set Alias" into a single Yes/No question to avoid redundancy?

Performing the operation "Set Alias" on target "Name: gcim Value: Get-CimInstance".
Performing the operation "Set Alias" on target "Name: scim Value: Set-CimInstance".
Performing the operation "Set Alias" on target "Name: ncim Value: New-CimInstance".
Performing the operation "Set Alias" on target "Name: rcim Value: Remove-cimInstance".
Performing the operation "Set Alias" on target "Name: icim Value: Invoke-CimMethod".
Performing the operation "Set Alias" on target "Name: gcai Value: Get-CimAssociatedInstance".
Performing the operation "Set Alias" on target "Name: rcie Value: Register-CimIndicationEvent".
Performing the operation "Set Alias" on target "Name: ncms Value: New-CimSession".
Performing the operation "Set Alias" on target "Name: rcms Value: Remove-cimSession".
Performing the operation "Set Alias" on target "Name: gcms Value: Get-CimSession".
Performing the operation "Set Alias" on target "Name: ncso Value: New-CimSessionOption".
Performing the operation "Set Alias" on target "Name: gcls Value: Get-CimClass".

[jasonmarcher]

Those are part of the built in CimCmdlets module.

If you say yes to loading WMI classes, then PowerTab will query the list of classes using Get-CimInstance. If you haven't already imported CimCmdlets in your session, this will cause that module to implicitly import.