ObjectNames already are property order independent because they use the
canonical name for comparison. We should not need a wrapper around it.
There has to be use of a non-canonical string somewhere to cause this
problem.
Ales Justin wrote:
This probably needs to be fixed in the ServiceControllerContext in
AS
code? We can do a simple wrapper around ObjectName name representation,
where equality is not dependent on the properties order. I can look at
that, np.