2,382 votes148 comments · Azure DevOps (formerly Visual Studio Team Services) » Administration & Licensing · Flag idea as inappropriate… · Admin →
We are committed to supporting the ability to move projects between collections, however we’ve been unable to make progress on this feature. Unfortunately, the challenges highlighted in earlier posts are still present.
I don’t foresee us making progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2019.
Azure DevOps Program Manager
2,638 votesMartin commented
I like the idea of a NotifyPropertyChanged attribute that causes a standard "if (a != b) ..." test to be generated but offers an override that can take an optional IComparer as a parameter for the more complex test and provide custom control over that test (generating "if (comparer.Compare(a, b) != 0) ...".
The NotifyPropertyChanged attribute would only then be allowed to be specified against automatic properties on a class that implements INotifyPropertyChanged.