All CLA requirements met.

I saw that and thought that test was only for aliases defined in InitialSessionState.cs, but looking at it again it also says it only checks default loaded modules, the CimCmdlets module is not automatically loaded by default.

Not sure if I am misunderstanding anything, but the aliases looked to be default, because it was set during the module load, so it's technically the equivalent of the user doing Set-Alias -Name "gcim" -Value "Get-CimInstance" when the module loads.

We have a list of modules in the test and explicitly load the modules.

Okay, thanks, just wanted to make sure. I've added tests for them now :)

That test doesn't fail locally here

@daxian-dbw @SteveL-MSFT Please check this PR. Do you have any theories why alias initialization for CimCmdlets module was previously done through manually calling Set-Alias? I guess there should be a reason for it looking strange like that...

@daxian-dbw @SteveL-MSFT Please check this PR. Do you have any theories why alias initialization for CimCmdlets module was previously done through manually calling Set-Alias? I guess there should be a reason for it looking strange like that...

So in PSv2, the AliasAttribute was decorated with AttributeUsage(AttributeTargets.Property | AttributeTargets.Field) so it wasn't yet able to be applied to classes. In PSv3 (I think), AttributeTargets.Class was added. Although the CIM cmdlets were added in the same version, my guess is that the additional attribute target was added later in development (or the folks working on CIM just weren't aware of it). If y'all found someone who remembers then feel free to ignore my theory 🙂

@thlac Thanks for your contribution!

🎉v7.1.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes