You surely have a reference for that bollocks?
Nope, but I didn't when VB6 was going down the pan either ;)
Just way too much software is working with it so Microsoft won't throw them away any time soon.
Microsoft did with VB6 and a lot more businesses relied on that for internal logic than they do with .NET now. Some of Microsoft's own products also used VB6 whereas .NET has never been embraced in Microsoft's products (other than perhaps plugins).
I am not saying that .NET technology will go anywhere since we have the open-source mono and products like Xamerin but I am very confident that Microsoft will be dropping 1st class support for their .NET implementation. Perhaps not in favour of Metro (since that is not doing so well) but if something "better" comes along...
Contrast this to the native Win32 API which Microsoft can't remove. If they did, Windows wouldn't boot. Even though Windows RT doesn't allow developers to access the full API, it is still there in its entirety since Office needs it and so does the low level underlyings of Metro itself (and everything else).