This is straight off of Hals Google+.
To get around to seeing whats buried in there with v3 you have to resort to a little trickery (calling the assembly itself...which references all exported objects...then drill down into the DLR indirectly). This explains why you are unable to see a "clean" list of TypeAccelerators in v3. For example, v3 shows the following with my hopped up command:
Now, to get a little more into the arcane side of all things PowerShelly, heres a little sidenote (and history): this was shifted from being a public class in v2 to an internal class in v3 as indicated by James ONeill: System.Management.Automation.TypeAccelerators broken in V3 CTP2.[PSObject].Assembly.GetType(System.Management.Automation.TypeAccelerators)::Get.GetEnumerator() | sort key | select key
To get around to seeing whats buried in there with v3 you have to resort to a little trickery (calling the assembly itself...which references all exported objects...then drill down into the DLR indirectly). This explains why you are unable to see a "clean" list of TypeAccelerators in v3. For example, v3 shows the following with my hopped up command:
and it returns:# Type accelarators[PSObject].Assembly.GetType(System.Management.Automation.TypeAccelerators)::Get.GetEnumerator() |sort key|select key|% {$_.key.ToString().Trim()}
adsiadsisearcherAliasAllowEmptyCollectionAllowEmptyStringAllowNullarraybigintboolbytecharciminstanceCmdletBindingcultureinfodatetimedecimaldoublefloatguidhashtableintint16int32int64ipaddresslongmailaddressNullStringOutputTypeParameterpowershellpscredentialpscustomobjectPSDefaultValuepslistmodifierpsmoduleinfopsobjectpsprimitivedictionaryPSTypeNameAttributerefregexrunspacerunspacefactorysbytescriptblocksecurestringsinglestringSupportsWildcardsswitchtimespantypeuint16uint32uint64uriValidateCountValidateLengthValidateNotNullValidateNotNullOrEmpty