I am now plannng to write a network program using DirectPlay.  I had been a Visual C++ programmer and I have some understanding on VB.  It seems that VB is more easy to create such an application with DirectX 7.  But I would like to know some more things before I go ahead.
1) Is there any performance lost or some other issues that I need to pay attention when using VB?
2) DirectX is COM based.  It is natural to let VB to use it through Automation, right?  Why Microsoft provide VB SDK only for DirectX 7?

Thank you for your attention
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

>any performance lost

oooh, yes....

>Why Microsoft provide VB SDK only for DirectX 7?

because VB support was not available before DX7.

DX7 includes a type library availble to VB, and also some ActiveX controls to make VB more accessible to the VB programmer. I believe (I'm not sure) that there was also a VB version of the
DX API reference.

NB the ActiveX controls and the type lib, last time I tested them, were not exactly *hot* on the performance front...

If you are au fait with C++, then do it in C++.

If you really want to write in VB, then may I suggest writing the Directplay portion as a COM component (ActiveX DLL/Control) in C++, then using it through VB.
HarveyAuthor Commented:
Thanks for the quick response.  But I still have some unclear issue

How poor the performance is when using VB?  I know VC using DirectX also through the COM architecture.  So, I think the performance is something similar to VB (The performance bottleneck is on the interprocess communication between the COM object), right?

How much time can I save when using VB?

If my application is only invloving some text information exchange, which one is suitable (VB/VC) when considering the performance/time issue?

Thanks again
>The performance bottleneck is on the interprocess communication between the COM object), right?


Of the 4 possible routes:

(in descending order of speed)        

VB/AX - Low Speed - Easy to Code
C++/API - High Speed - Harder to code

take your pick (but don't even bother trying C++/AX)...

In short, the VB/AX route is MUCH slower than the C++/API route, however,
I've never used DirectPlay, but I imagine it would be fairly light on the code side (compared to DDraw, D3D etc.), so if you're happy coding in VB then why not try the VB/API route?
LOOK, on today machins i think there is no BIG diffrence if any that can be tracked by user's eye in DDirectX oerformance via VC++ or VB.
The COM is the same and VB heavy usage of API->(C DLLs) is also the same and that's what counts.
VB is much more faster code writing rather then C++ *ONLY* to those who know *BOTH*.
for a C++ developer trying to *LEARN* VB - it won't be faster.
you have the 7.0 SDK (122MB) installed, you can find very good samples and tutorials for VB-DirectX7.0 on this path :
you've better d\l and install it....

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HarveyAuthor Commented:
Thanks for the comment
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.