C++/VB - VS2008 Managed C++ and DirectX March 2009 SDK build problems

Asked By AnotherPhilipTaylo

26-Mar-09 02:21 PM

Its driving me nuts - I have an updated C++ application that has a
DirectSound interface. The code has been converted to use managed C++ and now
compiles OK but fails to link - a typical error being

error LNK2020: unresolved token (0A00000D) IID_IDirectSound3DListener
followed by
error LNK2001: unresolved external symbol IID_IDirectSound3DListener

I can't find any documentation that relates to VS2008 managed C++ using
DirectX (including sample programs) so would someone put me out of my misery
and let me know whether this combination is possible and if so how.

As per the latest SDK, which still refers to VS2003, I have now defined
INITGUID and included dxguid.lib, but it still fails to link. I think the
answer is related to where these GUIDs actually live - within my app or
within a lib/dll.

Thanks

27-Mar-09 01:42 PM

schrieb

dsound.lib?


Armin

27-Mar-09 07:20 PM

[Please do not mail me a copy of your followup]

=?Utf-8?B?QW5vdGhlciBQaGlsaXAgVGF5bG9y?= <AnotherPhilipTaylor@> spake the secret code


Are you linking against dxguid.lib?
--

Legalize Adulthood! <http://blogs.xmission.com/legalize/>

28-Mar-09 07:11 AM

I prempted your dxguid.lib suggestion in my original question - the answer
is yes, I do link against dxguid.lib.

I have also performed a rebuild of the project with and without the INITGUID
definition. With INITGUID defined, the linker only seems to report missing
GUID_NULL.

Can I assume that the combination of managed VS2008 C++ and DirectX (March
2009) is valid and supported?

28-Mar-09 06:58 PM

[Please do not mail me a copy of your followup]

Sorry, I missed that in the original post.  Sometimes they get
over-eager to remove items related to deprecated components.  (I have
never used DSound, so I don't pay attention to it.)  You could try the
dxguid.lib from an older SDK.
--

Legalize Adulthood! <http://blogs.xmission.com/legalize/>