Please see my comment to the question. Even though anyone is free to create such a list, I don't think it could even be "official". The controls are not deprecated or claimed obsolete formally, even if some control is fully or completely superseded by a newer one. (I refer to
ObsoleteAttribute
, please see:
http://msdn.microsoft.com/en-us/library/system.obsoleteattribute.aspx[
^].)
I think such list just wouldn't make much sense. Look at it in this way: when you choose some available controls for your application, you need to consider its applicability to your design first, not being "cool" or "trendy". You are the ultimate decision maker, not the trend. And you always need to spend good time at it, much more then it would be required to check the comments about some newer control superseding the one you are reading about. All controls are more or less compatible with each other and can be combined in one design.
For a record, your assumption that the newer control superseding another one should be its descendant is not correct. It shouldn't. For example,
System.Windows.Forms.ContextMenuStrip
is not derived from
System.Windows.Forms.ContextMenu
, directly or indirectly:
http://msdn.microsoft.com/en-us/library/system.windows.forms.contextmenustrip.aspx[
^],
http://msdn.microsoft.com/en-us/library/system.windows.forms.contextmenu.aspx[
^].
—SA