Re: DirectX and Visual Basic... Bad combo?
- From: "Calab" <myspam@xxxxxx>
- Date: Sun, 24 Feb 2008 09:22:18 GMT
"Richard" <legalize+jeeves@xxxxxxxxxxxxxxxxx> wrote in message
news:O7Yu5IodIHA.2688@xxxxxxxxxxxxxxxxxxxxxxx
[Please do not mail me a copy of your followup]
"Calab" <myspam@xxxxxx> spake the secret code
<emHveZedIHA.3940@xxxxxxxxxxxxxxxxxxxx> thusly:
I'm looking to write a few small programs in Visual Basic.
VB6? You'll have to get a much older SDK that supports VB6.
VB 2008. No sense starting new projects using old standards.
For VB.NET, you can use the Managed DirectX API, or with more work,
the XNA Framework.
Looking online
(http://msdn2.microsoft.com/en-us/library/bb147348(VS.85).aspx) for some
sample programs, all I find are C++ examples.
Native DirectX APIs are best used from C++, that's why. People just
don't write high-performance graphics applications in VB.
I can tell... Trying to get some samples working in C++, but not having much
luck (as you can see in my other posting).
.
- Follow-Ups:
- Re: DirectX and Visual Basic... Bad combo?
- From: Richard
- Re: DirectX and Visual Basic... Bad combo?
- References:
- DirectX and Visual Basic... Bad combo?
- From: Calab
- Re: DirectX and Visual Basic... Bad combo?
- From: Richard
- DirectX and Visual Basic... Bad combo?
- Prev by Date: Re: Visual Studio 2008... Can't use ANY of the DirectX sample code?
- Next by Date: Re: Visual Studio 2008... Can't use ANY of the DirectX sample code?
- Previous by thread: Re: DirectX and Visual Basic... Bad combo?
- Next by thread: Re: DirectX and Visual Basic... Bad combo?
- Index(es):