Where did device in direct3D go?

I'm trying to do some of the real simple DirectX tutorials and when I try to enter the line:

Private Dev As Microsoft.DirectX.Direct3d.Device = Nothing

or it's equivalent for the C# version I get the error that Device is undefined. I am using the April 2006 DirectX SDK. I have added Microsoft.DirectX and Microsoft.DirectX.Direct3D references to the projects. For the VB version I use:

Imports Microsoft.DirectX
Imports Microsoft.DirectX.Direct3D

at the top of the file. For the C# version I use the "Using" equivalent of "Imports". When I am entering the Imports lines Intellisense pops up with each subsection such as .DirectX or .Direct3D. After I type the . after Direct3D the pop up list Intellisense has DeviceCaps or DeviceInformation, but not just Device. What has changed from the version that all of these tutorials use Should i use one of these instead of Device

Thanks for any help!

Answer this question

Where did device in direct3D go?

Michael Green - MSFT
I re-installed DirectX. Now I get "Device" is ambiguous in the namespace "Microsoft.DirectX.Direct3D". Any ideas anyone
Ewoud

Not sure. Is it just that intellisense is not finding it Does it compile if you type it in

(You know you don't need to type in the fully qualified name since you have the Imports statements)

This compiles for me (empty VB Express Class project).

Imports Microsoft.DirectX

Imports Microsoft.DirectX.Direct3D

Public Class Class1

Private dev1 As Microsoft.DirectX.Direct3D.Device = Nothing

Private dev2 As Device = Nothing

End Class
murpheux
I pulled up the MS tech specs for Direct3D and it lists Device so I think there is something wrong with my DirectX install. I'll remove and re-install. Even your simple example won't build for me.

Story of my life "...but no one else has ever had that problem, it must be something specific to your machine..."
ChrisC11

The amgious reference is becuase you refernced the MDX 2.0 beta instead of the MDX 1.1 released.

Now that you are on the 2.0 beta some things have changed names. e.g. Windowed becomes (I think) IsWindowed - look in the intellisense it should be pretty obvious.

However if you are learning I would recommedn you go back to MDX 1.1 where things are actually documented and the samples will work.

http://www.thezbuffer.com/articles/385.aspx
Eddie Deyo
Ok, Ok! I do eventually learn. After my last post turned out to be an ID10T (L)user error, I re-read Zman's info on DirectX 1.1 versions and such and I'm going back to using the April 2006 version 1.1 dlls for my learning efforts. Thanks everyone, especially Zman!
PrashantT
I removed the reference to microsoft.directx.direct3d and now device is ok. Instead, on:

Dim pParams As New PresentParameters()

pParams.Windowed = True

I get 'Windowed' is not a member of 'microsoft.directx.direct3d.presentparameters'.
The documentation for microsoft.directx.direct3d.presentparameters says windowed is part of it. Now what do I do

If I add the reference to direct3d back device causes an error again.

Thanks for any help
Joey.Net

There's nothing unprofessional or amaturish about it. Its a beta! Betas come in many many different levels of advancement and documentation. Yes MDX 2.0 is on the low side of this scale but the readme file in the SDK is very clear of that fact thats is a beta and has limitations. If you don't like it there is a released and documented MDX 1.1 in the same SDK.

If you've not already read Tom's blog on the future of MDX 2.0 then you should now: http://blogs.msdn.com/tmiller/archive/2006/04/12/575225.aspx
Scorpion Prince
Has anyone mentioned recently that you totally rock ZMan Because, well, you do!

Sadly, I am a foolish glutton for punishment and I intend to try to figure out things in the April 2006 version just out of sheer annoyance that Microsoft are so unprofessional and amaturish that they release things that don't work and/or are not documented.
Where did device in direct3D go?

Answer this question