R there anyone here using managed code?

The DirectX team is adding more and more Managed DX samples in each SDK release. There were additional C# ones added in both the October and December editions. Also, the documentation is being constantly revised, and is approaching a satisfactory state, IMO.

I think ManagedDX has a bright future. It's just taking a little while to take off, because of many reasons. For one, managed code is not portable to any other OS (ie the XBOX). Also, many feel that the API has just not developed enough yet. I think that you will see more MDX when .NET 2.0 is published, and when Longhorn is released. And I think you'd see it *really* take off if Microsoft made a console that supported .NET and Managed DirectX (XBOX3, maybe? [smile]).

So is it confirmed that X-Box 2 developers wouldn't be able to use managed code? Not that I plan on programming for the X-Box 2, but I think it'd be good to know for future preference.

I myseld use managed code, and love it. I definitly see a future for managed code though.

8)

Quote:

So is it confirmed that X-Box 2 developers wouldn't be able to use managed code?

I don't think any official announcement has been made on this front - most of what we know about XBox2 is speculation and rumour...

I did read an interesting article on the possibilities of getting .Net running on consoles. It would be difficult to get a full .Net VM running on a console, but you could (apparently) quite easily re-compile the .Net byte-code (MSIL?) down to a native binary that can run on a minimal console kernel.

The final conclusion was that it depends on whether Microsoft (or a 3rd party) want to do the groundwork for it... not whether it is (or is not) possible to do.

I'll see if I can find the article again (its quite old though).


Given how much of an investment Microsoft has put into it's .Net vision (both DX and otherwise) and how it keeps getting talked up as the primary "entry point" for Longhorn programming... I don't think it's going away any time soon [grin].

Jack

I seriously doubt it. I have limited knowledge of the Xenon, but I'm pretty sure it does not support .NET. Also, it is way too late in it's development cycle to add it. Pre-release developer kits are being released so the big dogs can pound out some games for Christmas 2005 [smile].

Quote:

Original post by circlesoft I seriously doubt it. I have limited knowledge of the Xenon, but I'm pretty sure it does not support .NET. Also, it is way too late in it's development cycle to add it. Pre-release developer kits are being released so the big dogs can pound out some games for Christmas 2005 [smile].

I doubt it as well. Just my point was that (unless I've missed something) they haven't confirmed/denied any particular feature set (hw or sw) for the XBox2...

Maybe it's something that might appear later in it's lifetime (SDK service pack?)... or not till XBox3, or not at all [smile].

Jack

What i'm sure is that the c# sample in the version of December sdk 2004 is less than the summer version~~.Now i'm considering of whether to reinstall the previous version sdk so that i can get on well with the c# directx programming.
Why do the Microsoft do this?

Quote:

Why do the Microsoft do this?

The SDK team are a decent bunch - they probably changed something either because they reckon whats newer is better, or based on feedback from people like us.

I've contacted the developers a few times now - always got at least a curteous reply (even the time when I made a blatant error on my part [embarrass]). If you've got a couple of decent examples and some sane reasoning then get in touch with them; you should at least get an answer saying why they've done what they did...

directx@microsoft.com / dx9beta@microsoft.com / DIRECTXDEV mailing list/ public DX newsgroups

hth
Jack