Well, apparently there is some concern about the messaging around DirectX 11 and Windows 8. Right now as of 5/11/2012 I am accessing DirectX via C++.
This means that if you are thinking about low level graphics design, then you may consider it important to get up to speed with Direct2 and Direct3 which are based on DirectX11, but are now installed with the Windows SDK The documentation on DirectX 11 is not a lot when it comes to the WinRT and so forth. The material is showing up at the URL: http://msdn.microsoft.com/en-us/library/windows/desktop/ee663275(v=vs.85).aspx.
This is bad for some who may have been using XNA or D3DX, but it sure is a good thing for people like me who got tired of the heavy lifting to maintain my DirectX version whatever, plus the distros. I enjoy a challenge and I am going to write about as time goes on.
Got to go, but I think I have the beat for hundreds of blogs over the next few months! Yippee for me! More junk for the Blogosphere!
(Changed Title around 6:36 since I modified the blog after writing the title)
So what about something like SharpDx ? http://sharpdx.org/
This seems to have a bunch of lightweght C# apis that wrap the Dx api (d2d/d3d etc) ...
And it appears to pass the app certification for Win8 ...
So C++ isnt the only way to use Dx in your metro apps!! ?!
There's not concern over the "messaging". There's concern over the functionality. They want direct access to D2D, D3D from C# or JS. It isn't there -- without a shim of some sort.
There's even bigger concern from the devs who adopted XNA and have been given a royal shaft and will flee from Win8/Metro. Glad I didn't invest any time in that sinkhole. Alas, I only went full-on into WPF and got the shaft there.
Sorry to be bitter but MS is losing us devs in droves (and I've developed Windows applications since 1991).
Sorry to hear about your disappointment with Microsoft. I hope you see that all of this change is to be more inclusive for our developers and partners. At least that is the way I see it.
Clearly the XNA situation may improve with the developers complaining, as well as other things.
But to be clear, XAML is not going away. HTML5 and JS is another pathway now. C++ has returned with the XAML and C++.
I haven't looked at sharpdx.org, but this is the kind of thing that is needed and the kind of thing that the communities do best. The goal of C# was to have a language that was under ISO control that communities would rally around.
In my humble opinion this would be the best thing for Microsoft's long term goals and that is to have a well designed language like C# be used by open source as well as Windows. This would counter situation that we see with Java.
I also expect xna or similar in windows8 metro with c#. Not delivering that is like delivering MS Word without the ability to insert pictures. It's not new. it's not different. it's not "inclusive". It IS "not done".
Don't agree, not delivering the ability to insert pictures in Word is not the same as not delivering XNA in Windows 8.
As to why XNA has faded away, there are better people then me to answer that question. If for some reason it is in the final version of Windows 8, I will welcome it. If as it appears that it isn't in the beta releases of Windows 8 design tools, and I can live with that.
I am glad to get back to C++ and have no problems with that.