Managed DirectX .NET Framework 2.0 horribly breaks DirectSound 1.1

[Tom Kreyche]

If you want a good laugh, follow the instructions at
msdn.microsoft.com/directx/sdk/ for the Dec 05 SDK, about using Managed
DirectX for .NET Framework 2.0 (Beta).

Try compiling one of the Managed DirectSound examples originally built using
1.1 and see how many things break, and then check both versions in the Object
Browser -- there are many significant changes--glad I didn't try building a
product on 1.1.

The docs in the Dec SDK are for 1.1 and are from the Aug SDK - anyone know
when they will be updated for 2.0? Since 2.0 is supposed a beta for managed
DirectSound, is it worth or safe using at all?

Tom

Tom

[Chuck Walbourn [MSFT]]

The managed documentation is being completely rewritten for the 2.0 version
of managed DX, and will likely be available in the April 2006 DirectX SDK
release when the assemblies themselves RTM. The existing managed docs cover
1.1. only. The MDX components themselves have been updated for the upcoming
Feburary 2006 DirectX SDK release, and are near final versions.

There are some issues with the way VS2005 is choosing which version of
assemblies to build with by default, which complicates things if you had
installed beta versions of the .NET 2.0 CLR itself or Beta versions of VS
2005. Cleaning out the older versions of the assemblies from your system
helps, as does explictliy choosing the right assembly versions for your
project within VS 2005.

--
Chuck Walbourn
SDE, Windows Gaming & Graphics

This posting is provided "AS IS" with no warranties, and confers no rights.