2,800 votesSC commented
Or even better, automatically do this for overridden methods when no documentation is supplied.
1,321 votesSC commented
The history around managed DirectX is basically a graveyard. First we were promised VB support via type libraries and documentation, but it was abandoned in the next release. Then C# support via Managed DirectX - which was abandoned due to a lack of support for the developer working on it. Next was XNA, which was never well thought out and was killed when the larger game developers complained about Windows Phone.
It's aggravating and makes me extremely bitter towards Microsoft. The real irony here is that a large number of the great indie games on Windows 8 (basically some of the only games on that platform) are written using open source copies of XNA.
Although my ideal scenario would be full and official long term support for DirectX in .NET, a more realistic option would be to convert DirectX to a WinRT library that's part of the Windows platform going forward. That way there's no performance hit to C++ apps, but .NET applications get the full version without any risk of it being "canned' 2-3 years later which has historically been the norm.
Windows is getting beat up by iOS - for the first time in my life Windows is now the "have not" platform. Requiring all game developers to use C++ is a dead end for the smaller publishers that have been flocking to alternate platforms. Unity support is nice, but doesn't allow the full range of possibilities that would be opened up with DX WinRT.SC supported this idea ·