The new powershell feature “ordered” hashtable (a new PowerShell feature in v3. See OrderedDictionary Class) becomes an ordinary hashtable when it is imported via Import-CliXml. There is a “active” bug on Microsoft Connect OrderedDictionary becomes Hashtable when exported to and imported from clixml but no action for a couple of months. As a workaround do not use ordered hashtables but use an array of normal hashtables.
Recent Posts
.NET
ADO DataServices
Api
Authentication
AutoMapper
Azure
biz.dfch.PS
biz.dfch.PS.Storebox.Api
biz.dfch.PS.System.Logging
biz.dfch.PS.System.Utilities
biz.dfch.PS.vCAC.Utilities
biz.dfch.VCO
bug
C#
ChargeBack
CI/CD
CodeContracts
CTERA
Cumulus
DataServiceContext
EF6
EnterpriseArchitect
EntityFramework
EWS
Exchange
Expressions
GitHub
graylog
graylog2
java
javascript
jaydata
JetBrains
jQuery
JSON
JustMock
LightSwitch HTML
LINQ
log4net
MEF
MetaModel
MicrosoftConnect
NoBrainer
NSX
NSX-V
NuGet
ODATA
Office365
PowerCLI
PowerShell
REST
Scheduled Task
SignalR
SOAP
Sparx
SQL
StructureMap
System.Diagnostics
TeamCity
Telerik
Testing
Toolchain
vcac
vCAC52
vCenter (VC)
vCloud Automation Center (vCAC)
vCloud Director (vCD)
vCO
Visual Studio
VMPS
vmware
WebAPI
WebClient
WPF
XML
1 Comment »