Microsoft went through some trouble developing the DX7 type library for Visual Basic programmers, but with .NET you''ve got to wonder whether or not they will continue to do it for DX8. My thinking is this: the next version of VB (VB.NET) will not compile to native, platofrm-dependent machine code. The only language that will do so in Visual Studio .NET is VC++. For enterprise applications, this is fine. But where performance is a factor, VB''s loss of a true compiler just plain sucks. And since DirectX was developed for high-performance multimedia, DirectX under VB.NET makes utterly no sense. FYI, the other languages (i.e. VB) will compile to MSIL, or Microsoft Intermediate Language, which will then be interpreted by the .NET Common Language Runtime. ...not that I often use VB for DirectX apps, but I have been messing with it lately, and the thought just struck me.

I don''t think M$ will remove the native-code compilation for VB7. They are upgrading DX8 for VB, and I know because I''m on the beta program.

I''ve seen the ''official'' code for using DirectX in VB.NET so I know it still supports at least DX7. I wouldn''t think that they would stop making DX non vb compatible (out of the box, so to speak) and also I agreee that they would be pretty stupid to get rid of the native compile option. Especially since both VB and VC++ use the same compiler.

(The above information is undoubtedly incorrect, so flame/correct {probably more civil} me as you see fit)

Trying is the first step towards failure.

quote: Original post by ragonastick
Especially since both VB and VC++ use the same compiler.
Trying is the first step towards failure.

Hmm... maybe that what''s wrong with VB... It''s really trying to compile C++ code!

No, but seriuosly, the compiler is quite diffrent. The linker, however is the same.