I just started working again on a game I had been writing and abandoned for quite a while. I have managed to get it working with the latest release of the SDK but now I have run into a problem trying to add a new UI.
Im am trying to add some of the the controls from the customUI tutorial that came with the SDK . I added "using Microsoft.Samples.DirectX.UtilityToolkit;" to my code but of course the compiler didn't reconize Microsoft.Samples...
After some googling I realized I had to include the files from
"Microsoft DirectX 9.0 SDK (October 2005)\Samples\Managed\Common" in my project. the problem is when I do this and try to compile I get dozens of errors such as
The namespace 'Microsoft.Samples.DirectX.UtilityToolkit' already contains a definition for 'SettingsDialogControlIds'
The namespace 'Microsoft.Samples.DirectX.UtilityToolkit' already contains a definition for 'SettingsDialog'
etc.. etc...
What am I doing wrong im sure it is something very simple but my C# is rusty at best.
How can i go about accessing Microsoft.Samples.DirectX.UtilityToolkit from my app
using Microsoft.Samples.DirectX.UtilityToolkit
Hot Topic
- Might it be a BUG within DXUT?
- MDX: Desktop or Laptop?
- Texturing, how to disable
- non-FVF VertexBuffer
- Why does my window go blank after a resize?
- Device->UnmanagedComPointer
- My system slows down when I turn on Reference rasterizer
- Debugging program that won't start
- Mesh.FromStream method of C#
- Getting rendered graphics (quickly) from the card
Game Technologies
- Install the managed DirectX files from the redistributable Package
- GoogleEarth-like textures assignment ?
- How to create a new Texture from an existent Texture?
- New Managed DirectX Game Demo - Xiiris Arcade - Your Daily Space Shooter Dose 8)
- .X Files, Baked Textures & 3D Studio Max
- Duplicate Item "Resources" parameter error
- Help with a simple Direct3d Program
- Visual Basic vs Visual C++
- Vertex buffer best practices for particles
- Getting rendered graphics (quickly) from the card
using Microsoft.Samples.DirectX.UtilityToolkit
Prdkv
dxmut.cs
dxmutdata.cs
dxmutenum.cs
dxmutexception.cs
dxmutgui.cs
dxmutmesh.cs
dxmutmisc.cs
dxmutSettingsDlg.cs
and then a second set prefixed with a "w"
wdxmut.cs
wdxmutdata.cs
wdxmutenum.cs
wdxmutexception.cs
wdxmutgui.cs
wdxmutmesh.cs
wdxmutmisc.cs
wdxmutSettingsDlg.cs
Why are there two sets I am using the first set and everything seems fine.
mbauman
Have you possibly added the files more than once
Have you added a reference to a compiled DLL which maybe has those files included
Grisu
Evgeny0
Of you are using the Managed DirectX for .Net 2.0 beta (v2.0.900.0) then you use the ones beginning with w. If you are using the Managed DirectX for .Net 1.1 (v1.0.290x.0) then use the ones without the w