When checking disassembled code that was exported using .NET Reflector, I noticed that the order attributes for any given object are not always supported.
I saw this when comparing the disassembled code of two versions of the same assembly (with some minor code changes between the two versions), in classes that did not actually change between versions.
eg.
[WebBrowsable, Personalizable]
public int SomeProperty ...
against
[Personalizable, WebBrowsable]
public int SomeProperty ...
This is rather inconvenient, since it looks as if the files that have not changed have.
What controls the order of the attributes in this scenario, and is there anything that can be done to maintain order?
source
share