Hi,
I have a DX application I've been working on for a while with .NET 1, however I want to upgrade to .NET 2 for generics and (does it have templates ), so will the upgrade affect the application at all Will I experience any problems What do managed dx9 2 and dx10 offer related to this. Will I need either as well, and what benefits and problems will there be in upgrading these in the middle of my project. Is it worth the upgrade
thanks again
.NET framework 2 & DX
KenRumble
Hello,
Well, there was some work underway to bring Managed DirectX up to the .NET 2 platform, but as of the GDC2006 Tom stated that these MDX 2.0 assemlbies will be part of the XNA Framework and as such will not be released in their current form. What this means exactly, I'd like to know as well, but I guess it's safe to assume that a final release MDX 2.0 will be a good long while coming and since the current MDX 2.0 release shipped with the SDK is still in beta, I wouldn't use it just yet.
You can however use the MDX 1.1 assemblies in your .NET 2.0 applications. Other than a performance hit when debugging in Visual Studio 2005 and some (minor) occasional quircks, you should be good to go.
As for Direct3D10, that's also still in beta, so a definite MDX wrapper for it from MS also won't coming up any time soon. One of the regulars at GameDev.net is working on a preliminary test wrapper for D3D10 though and if all goes well, we should have a first article on this up on mdxinfo.com this week. D3D10 however will only be available on Vista and there's no hardware available for it yet, so you really only can get your feet wet atm, but do no real development.
So to cut this long story short, I'd go with MDX 1.1 on the .NET 2.0 platform, if you need any .NET 2.0 features. Otherwise, I'd stick with good ol' .NET 1.1