Update:  This behavior has been corrected in the RTM version.

I had been experimenting with and using the PowerShell 5.0 Preview from April 2015 and generally enjoying the experience.  I had even forgotten that I was using the preview during day-to-day usage.  The preview, in my mind, is exceptionally stable, and I can't wait to see the RTM version.

Therefore, imagine my frustration when my Add-TypeAccelerators script ceased to function.  This script was designed to add type accelerators to the PowerShell session.  For example, if you use System.Collections.ArrayList quite a bit in a script, you might like to have a shortened version like [AList] to use instead.  In order to achieve this, you have to be able to add your type accelerator reference to the dictionary located under System.Management.Automation.TypeAccelerators.  This dictionary was public and accessible in PowerShell 2.0, and you could just call its static Add method:


In PowerShell 3.0/4.0 this was made private, so according to this Hey, Scripting Guy! Blog article, the way to achieve this was to use the PowerShell assembly to retrieve the type, store it in a variable, and then call the Add method:


This was successful and can be seen when accessing the TypeAccelerators static Get property:


It's there at the bottom and we are free to use it like any other type accelerator...until the 5.0 April 2015 Preview when calling the TypeAcclerators static Add method still resulted in a successful addition to the dictionary, but even though it is listed, it is not usable:


Now, we'll have to do some digging.  Checking the reference source on MSDN only provides us with the static Add and Remove methods, and the static Get property.  What about the underlying private fields of the TypeAccelerators class?  We can find those:


The output from that is quite a bit, but the important matter is there are three FieldInfo objects returned with the names builtinTypeAccelerators, userTypeAccelerators, and allTypeAccelerators.  By the way, the binding flags are there because, by default, GetFields and GetField only return public non-static fields.  Let's see what's in the userTypeAccelerators:


We now know that anything we add to the dictionary is going to be ultimately stored in the userTypeAccelerators field, all the built-in accelerators are ultimately stored in the builtinTypeAccelerators field, and the combination of the two is stored in the allTypeAccelerators field.  

Apparently, it is the builtinTypeAccelerators field that the PowerShell engine is using in the preview to reference its valid type accelerators.  To fix our problem, we just need to get our user defined accelerators into that field without overwriting the ones already there, so let's just replace builtinTypeAccelerators with all the entries in the Get static property:


And now, let's try our user defined type again:


Success!  It's the little things.

Disclaimer:  I do not know if this will change and become even more difficult in the RTM, or whether it will be reverted back to the behavior of PowerShell 3.0/4.0.  For now, as of the PowerShell 5.0 April 2015 preview, this method works, which I'll condense down into the four lines necessary once all the research and digging are stripped away:


I hope this helps.