whoopee, ".Not" got something that C++ already had for, like, EVAR
No matter how much Micro-shaft tries, they'll NEVER replace C++ and native Win32 calls with their bloatware ".Not" no matter WHAT they call it.
And I'd be better off targeting GTK or Qt if I want cross-platform. Trying to shoehorn ".Not Core" into POSIX operating systems is laughable, at best, frightening at worst, and yet another "Embrace, Extend, Extinguish" attempt to those of us who actually KNOW better.
I was a total Microsoft Windows fan up until the announcement of the ".Not Initative" when Ballmer took the reigns. The 1997 PDC here in San Diego was the last conference I went to. I instinctively knew that Micro-shaft had made a sharp turn and was heading into the WRONG direction.
So the idea that they've taken something that worked really well in DevStudio for C++ applications ('data changed' breakpoints, something I have made use of before, LONG ago) and _FINALLY_ got around to putting into the ".Nonsense" side of things, it's no great accomplishment. Wheee.
I got used to MFC with the old 'Visual C++" stuff, back in the 16-bit days, even, and I think *THAT* IDE [which was VERY typist-friendly] is STILL BETTER than anything that Micro-shaft has produced since they went all VB-ish with their "properties" windows for dialog controls, etc.. Class Wizard and dialog control properties, the way it was in DevStudio '98 (pop-up tabbed dialog boxen) was MUCH easier, especially for dialog boxes.
Anyway, I've always liked the integrated debugger, having had to use CodeView before that, with dual monitors even. But I don't do C-pound nor ".Not" and so it's no wonder I didn't know the features were missing...
Icon, because this is all like "whoopeee" and "wheeee" without the exclamation points, bold text, nor capitalization.