I'm having a problem compiling due to the compiler finding the .dll in two different places since updating my DirectX version. Here's the specific error...
Error 1 The type 'Microsoft.DirectX.DirectInput.Device' exists in both 'c:\WINDOWS\Microsoft.NET\DirectX for Managed Code\1.0.2902.0\Microsoft.DirectX.DirectInput.dll' and 'c:\WINDOWS\assembly\GAC_32\Microsoft.DirectX\2.0.0.0__31bf3856ad364e35\Microsoft.DirectX.dll' C:\Documents and Settings\Joe\My Documents\Game Programming\MegisShell\GameDriver.cs 61 47 MegisShell
How do I make Visual Studio 2005 point to the correct one Or is it something more than that Please help, thanks!
Compiling issues, DirectInput .dll is in two different places
Hot Topic
- Create an Overlay Text on Games...
- Mesh Intersect Confusion
- Pixel Perfect collision Detection
- i need help! pls I want to begin to write games
- mesh texture color
- Strange Behavior from GetTechniqueByName():SetTechnique()
- DirectX Area inside a CLR/WFA or MFC window?
- Terrain Rendering
- XACT question pertaining to ambient soundscapes
- XACTENGINE_E_INVALIDDATA due to wrong version being used
Game Technologies
- Engine Architecture
- XFiles & Transforms
- DirectX with Java?
- Taking hi-res screenshots.
- Problem with point lights in D3D9 Managed Code
- How do I Setup Visual C++.net 2003 Standard for Direct X Games Programming
- MDX SDK Framework - Copyright?
- DirectX and Visual C# .NET Express???
- StateBlock in Managed DirectX using C#
- PostProcess with MultiSampling
Compiling issues, DirectInput .dll is in two different places
Jayzzz
Yes thats exactly what it means.
for MDX 1.1 there are multiple assemblies
for MDX 2.0 all the namespaces are included in a single assembly. This is why you get the duplicate error if you add some of the old MDX 1.1 references. Things exisit in both places.
Clark Snowden
Does that mean that if I was to include DirectX v2.0.0.0 that I wouldn't have to add DirectX.Direct3d because it's included in DirectX I'm slightly confused with this. Are both version interchangeable
David Barbour
This is a common problem and has been answered several times in the forums. What is happening is that you have references in your application to both the MDX 1.1 system and the MDX 2.0 system, Remember that if you are using the MDX 2.0 system (In Beta) that you only have to reference the one assembly. If you are using the MDX 1.1 system you still have to reference all of the DirectX Assemblies that you will need, making sure that they are not the version 2 assemblies.
Have a look at the following FAQ post on www.thezbuffer.com.
http://www.thezbuffer.com/articles/385.aspx