If multiple attributes are applied to a member, e.g.
[Foo] [Bar] void Baz() { ... }
Then are any guarantees made by the CLR/.NET specificat
imo Attributes shouldn't have an order as they're not flow control constructs.
I guess you could add a priority property to the attribute and use that to determine the run order?