tick tock CA... chickens coming home to roost.... and we use visual studio 2005....Technical debt is growing.
BUT in the end as plex users creating your software the buck stops with you in the eyes of your end users I suggest...end users wont accept the excuses that CA were paid support money but did not deliver, end users will ask why you did not realize this earlier and taken evasive action. We as Plex users have witnessed for years now the total lack of investment into the c++ generator, the writing has been on the wall for years, and whether you disagree or agree on CA current strategy you will in then end will get the sharp end of the stick. My advice would be to plan for a continued behavior by CA and plan for a contingency c++ plan, this way you cover both eventualities.
If this was a new behavior by CA of neglect then may be user pressure I would accept would be realistic but there has been years of pressure and nothing has occurred so if your end users / management become aware of this prolonged years of pressure and no result then this will again lead end users / management saying "yes you did complain about CA but why did you not do something after it became habitual the behavior"
(For the record I believe CA should support current Windows OS if a Plex customer pays support and should not need voting or enhancements or ideas or user intervention or divine intervention)