3 votes for this. I've been using SharpDX for a while now, but it should be Microsoft providing official support for DirectX using C#. DX is almost a part of the Windows Runtime now, but you haven't taken the final step to fully integrate it, we have to use very weird interop interfaces (If I understand it correctly). Just remake DirectX 11 and 12 to be part of the runtime so that it's available for C# developers. There may be some issue with such a change, but I'm not aware of any.
Vector2 class is a good example for me of why this should have already been done. Typically a Vector2 class (take a look at Numerics.Vector2) will have a range of static methods. But does it have Angle() CatmullRom() ClampLength() Constrain() FromRadians() GetNormals() Hermite() Project() etc.
It just makes sense doesn't it, the same amount of sense as providing basic extension methods.
This still hasn't been implement, it's now mid 2017. Am I missing something ?
No, absolutely not. This would be a huge long term business mistake. OpenGL and Vulkan should eventually be removed from the Windows ecosystem. They aren't required to make Windows games. And it's no more diffucult for a dev to write DX software. If devs want to develop for Android they will use OpenGL. That doesn't seem to affect their decision making about releasing for Windows ... Pokemon Go for example .. iOS/Android only. Probably written with OpenGL, but did they release it for Windows .. no. So the argument that it makes it easy doesn't seem to be a real argument at all. Their are other more important reasons that devs decide for/against releasing on a different platform. The ecosystems are completely different. Having an open graphics API makes no difference.
OpenGL and Vulkan are nothing more than poison to the Windows ecosystem.
This is way too ambitious, and unnecessary. For instance, Legacy Windows should absolutely not be supported. I don't want Microsoft wasting time and money supporting and integrated current and new technologies into Windows XP/7 etc. Microsoft doesn't have infinite development potential. There's still so much work to do on the platforms they support now. This list is just a ridiculous burden to put on them with very minimal returns.
I feel like Android developers completely ignored Windows Phone and still drag their feet when it comes to bringing their apps to Windows. Why should Microsoft support the Android platform beyond making it easier to move to Windows or use Windows for development. My last two phones were Windows Phones, not only did i experience it for myself but it's well known that the windows store has taken a long time to get moving. It's just starting to pick up now. No thanks to Google or the Android community.
Seems like MS would be helping a platform that overtly ignored Microsoft's mobile platform and who's community members publicly denounced Windows and wished it to ****. And I'm not joking about that, there are many people that bear HATRED towards Windows, and most of them work with Linux and Android. It might not be representative of the entire community but the public face of the Linux/Android crowd is an angry mob, who show no respect for other operating systems, who think they are working with God's own tools and would wish Windows to be destroyed and everyone at Microsoft burnt at the stake.
The only way I would think this is a good idea, is if Microsoft released their own Linux based mobile platform and implanted the store and tools in there.
And I have just noticed that when FieldOffset is used, both layouts need to be initialized. That doesn't make sense to me at all. It should be enough that the memory is fully initialized, the overlayed layout is an abstraction !
@Aravind - this is a VS feedback site, not a developer forum, try: http://www.gamedev.net/page/index.html
I would have thought this would get more love. It seems like a no-brainer that xaml should be available for desktop development.