VC++ versus VB
[493 byte] By [sea kayaker] at [2007-11-17 13:29:59] 
My company is about to begin a new project (Auto & Home Insurance -- Application, Rating, etc. -- a case where somewhat complex data structures are needed). Some people in my company believe that Visual Basic would be the best language to use. Those people, however, are mostly COBOL users. I am partial to Visual C++, (most of my prior experience was with C, with some Microsoft Quick Basic back in the dark ages). What are some of the pros and cons of Visual Basic compared to Visual C++
# 1 Re: VC++ versus VB
This debate was already held and maybe you should scan the old archives. If they "survived" the transfer of the system.First of all you should know that development decisions are taken based on business objectives rather then technical issues. The fact that the majority of your developers might be familiar with VB is much more important then the technical excellence acieved by VC++.
+/- list:
VC++:
=====
- offers entire set of OO techniques (templates, etc...), while VB/COM offers just a small subset,
- portability (using STL, std. C++),
- availability of existing and proven tools and techniques for large scale projects,
- seasoned C++ developers tend to be greater professionals then VB developers who are in many cases "automatic programmers" (find a solution to a problem and constantly reuse it because it "works", improvement is not a word in their vocabulary).
VB:
- easy to learn,
- RAD,
- database support,
- COM support.
In case you can't decide between VB and VC++ and both are new platforms in the company, Java is exactly in the middle now with improved support for UI (Swing) and IBM's San Francisco framework of business objects.
Tomaz Stih at 2007-11-9 12:09:18 >
# 2 Re: VC++ versus VB
Thank you for your most useful response. I found the discussion threads and found them very useful as well. I've been away from software development for a while and I have a very dumb question: What is "RAD"?sea kayaker at 2007-11-9 12:10:19 >
# 3 Re: VC++ versus VB
We have to start work on a considerable big project(which involves data communication, TAPI). Again there is mix breed of programmers (VB and VC). I myself is interested in pusuing it in VC but others are interested in VB. Is there any way that some of the module can be programmed in VB and some in VC and then integrate both of them. If so how how will we make individual modules and how to integrate them, what will be the prefered interface?
Thankx
Shahzad
Shahzad at 2007-11-9 12:11:15 >
# 4 Re: VC++ versus VB
RAD means Rapid Application Development.Eddie Velasquez at 2007-11-9 12:12:21 >
# 5 Re: VC++ versus VB
One Way to do this is to take your low level calculations or routine that the VB developer is never expected to modify and write them as a DLL in VC++. The Visual Basic application can link to the DLL to call the routines. There are some considerations. E-mail or respond if you want more info.Brad Cadle-work at 2007-11-9 12:13:20 >
# 6 Re: VC++ versus VB
In an environment you described your modules will typically use COM to communicate.For example you will use C++ for some low level system tasks and have VB main app. You will write your objects in C++ and provide interface to the outside world (automation support) using ATL or MFC or both.
COM objects can also be written using VB classes and used in C++.
They can also be distributed over several machines almost transparently.
The combinations are limitless.
tomaz
Tomaz Stih at 2007-11-9 12:14:19 >
# 7 Re: VC++ versus VB
Yes I would like to get more info about it. Is dll the only way to make these routines, and the big problem is how do we split up the whole project in small routines?. Are there any guidlines for this?thankx in advance
Shahzad
Shahzad at 2007-11-9 12:15:16 >
# 8 Re: VC++ versus VB
Large Scale C++ Software Design by John Lakos is one of the C++ bibles. Based on your questions for a large project I am warmly recommending you to add an experienced VC++/VB consultant on your team.Tomaz
Tomaz Stih at 2007-11-9 12:16:19 >
# 9 Re: VC++ versus VB
Rather than comparing VC++ to VB, I would suggest that you read the book "Surviving Object Oriented Projects". The name of the author escapes me at present.The author suggests using C++ with EXTREME CAUTION. In fact he advocates investigating using other OO languages over C++.
Personally, I prefer C++; but, I define a "rational subset" of the language - features that I feel comfortable using, and features that I feel do not increase complexity beyond their benefits.
If you want to see how NOT to program C++, examine the articles "Obfuscated C++" in C++ Report.
VB is a great language. It will probably be sufficient in a great many cases. However, it has been my experience that eventually you will come across problems that are difficult to solve in VB.
Also, check out the number of books about using the Win32 API from VB.
kmontgom at 2007-11-9 12:17:17 >
# 10 Re: VC++ versus VB
Hi.Before you ask us which is better VC++ or VB, you need to focus your company situation.
If you devleop the new project, your company will hire the new programer of VB or VC++?
If COBOL programmer have to learn VB or VC++, VB is better choice since VB is easy to learn.
If this project will be expanded the huge application with ActiveX control, VC++ is better.
If some company is working on Unix and WindowNT, this company tends to use VC++ since Unix programmer is familiar with
C++, he or she can learn VC++ easily.
If we learn VB, we only work on Window OS. This is a big disadvantage.
Personally, I prefer VC++ partly because we have a chance to learn Java. But on the company point of view, which is better?
Hire the new programmer? Train the exising COBOL progarmmer? and so on.
My opinion seems not to help you, but we don't have to select the computer language by the individual taste.
HTH.
-Masaaki Onishi-
Masaaki at 2007-11-9 12:18:27 >
