deterministic ordering of initializecomponent in windows forms designer
When I make an edit to a winforms file, often the designer reorders properties, etc. Instead, the designer should do one of two things:
* attempt to preserve original order
* define a deterministic ordering of properties designed to minimize reordering (e.g., sort by field name). The first people who use a version of VS which does this will experience heavy editing of files the first time but subsequent changes will have nice, small diffs and merge more easily.
The way designer works currently seems to be nondeterministic. So, e.g., setting CancelButton on a Form results in the order of initialization of unrelated controls being changed, resulting in a lot of VCS noise/churn.