Printable View
Hi all,
what are the benifits and possibilities of VB 6?
I know there are so many benefits and possiblities using VB 6.
Let's each and everyone of us post here a point. So, many beginners will get benefits from that including me.
My mind is always asking me what you can do with VB and what you can't. So, keep my mind clear I posted this thread here.
I know we can write a small book for that. But, post here your thoughts sweet and short.
Thanks in advance.
Compared to what?Quote:
Originally Posted by csKanna
One of the big DETRIMENTS is that it's no longer supported.
You can write a program to do just about anything in VB. The question is, "is VB the best language to write this application in?" I can write a multiuser operating system in VB but it would be too slow and too large for anyone to use. OTOH, I could write a little database handler in assembly, but it's much faster to write it in VB and the speed and size are no problem.Quote:
My mind is always asking me what you can do with VB and what you can't.
VB6 is, as best I can tell, a beginner's portal to the programming world. It's a "hold your hand" kind of language. Not hard to pick up, but it has potential. The biggest restricting factor that I've encountered is that it doesn't let you go. It's always holding your hand. And yes, while it's possible to construct games in VB, even to the point of DirectX 3D applications, they run so much better when programmed in a language designed for that kind of thing. I'm just starting to migrate away from VB6 for precisely that purpose. VB is just not powerful enough to do what I am going to be needing of it, and I don't want to spend years with VB to reach the end and discover I can't do what I want to.
But for home applications, simple games, stuff of that nature, VB is a good language. Not too complicated, but you have to know how to code if you're gonna get the best results out of it.
On my last job I designed what was basically a GUI to a database, that had over 5 million lines of VB code. It wasn't very "limiting".Quote:
Originally Posted by timeshifter
I used VB6 to write a client server application. String handling was soo slow in VB6 compared to vb.net we had a 60% increase in speed when moving over. It wasnt limiting, but definatly slower.
Moved.
... where??? :confused: :confused: :confused:Quote:
Originally Posted by timeshifter
Number of line is irrelevant - someone may write 1K lines that will output the same result as say [a = b ^ 2] ... ;)Quote:
Originally Posted by Al42
VB6 was a good tool for its day and there are still a ton and a half of commerical software products out there written in VB6.
That is slowly changing. If you are just getting into the programming world, .NET is the way to go.
Benefit? You don't need the .Net Framework Installed. :wave:
If you are a new programmer then Id learn something else, really depends on what industry you are in. VB6 is perfect for what I do right now though, small simple programs, admin tools, self executables, etc, for XP only. Even made a Remote Video Program for a popular DVR, but using an external ActiveX Control. Eventually Ill need C++ though .. and some linux .. due to my industry. Not sure when they will move to .Net .. probably take a couple years.
Thats not really a benefit, as you need the VB6 runtime installed. Including the correct versions of DLLs, which is actually a huge huge problem, not a benefit.
the VB6 runtime comes with XP .. no need to install an extra 20MB file.
Utilizing APIs and WMI, you dont need 3rd Party DLLs for all apps.
You can also simply update the current DLLs to the newer ones if required.
.Net comes with Windows 2003+
And it will come with all new OSes in the future, so there is still no benefit for future.
I release VB6 and .Net apps in the same package, and believe me the .Net one is much much easier to install. You pick the files you want to install and thats it. VB6 I have to include about 5 merge modules, numerous DLLs that have to be registered and that causes problems with upgrades and keeping signatures the same for version compatability.
To add, the install does the .Net install for me, so its no hassle what-so-ever.
Most people dont use Windows 2003+ and XP will be around for a long time yet. The .Net framework will still require updates. Also, its not difficult to update a DLL file. Nobody can predict the future, including Microsoft. BTW this thread topic is not about .Net. ;)
PS. How large is your .Net file (the whole installer package).
If you have released VB6 apps and have no issues with installs, then I envy you ;).
There are no benefits to using VB6 over .Net at all, I have used both for 7 years (well 6 for .net) and released numerous apps.
Its easier to understand VB6, so new coders can get straight into it without having to really worry about OOP and form instances and the like, which seem to be the main problem for people converting over to .Net. I believe its now free to get the VB6 environment (dont quote me on that), so thats another benefit.
Its 118 Meg, of which 40 meg is setup including MSI engines and service packs, .Net and service packs, merge modules (MDAC 2.7 which is about 8 meg i think). Most of the rest is actually manuals and documentation. The .net apps are much smaller than our main VB6 app which comes in at 5 meg on its own.
Never once had a problem. I also create update patches for them which work flawlessly. That said I don't use the VB6 P&D.
110Mb? Thats huge .. my apps are typically around 2-4MB.
But you are probably creating different apps than I am.
I'm using InstallShield 12 (this very second actually) and trying to upgrade VB6 files, and it refuses to register them half the time. That could be a user problem however, I dont trust IS12 very much.
I use Inno when I need an installer, but most of my apps these days are self executables, which is perfect with VB6, small 40kb average files.
Aye, VB6 is great for small apps and single coders, expanding it out to a larger app with multiple developers brings in a few issues of its own but its still usable.
Yep i'm a single coder.. :)
That's really a HUGE understatement - it's just a tip of an iceberg though... :p :rolleyes:Quote:
Originally Posted by Grimfort
I was with you until now - lots of major entireprises were built using VB6 by small and very large teams including architects, developers, ordinary coders and others (largest team I was involved included some 150 members !!!) so I'm not sure were did you get that idea from... :confused:Quote:
Originally Posted by Grimfort
That is so not even close to being accurate.Quote:
Originally Posted by Grimfort
My company has a number of applications, commerical, that are huge in scope and sell for 6 figures, all written in VB6 by teams of programmers ranging from the US to India. Our Visual Source Safe database is global.
Our .NET versions are just now starting to sell, but we anticipate a continuing market for the VB6 versions for several years to come.
I only said it had a couple of issues but its very usable. I use VB6 within a team, have you tried editing the same form at the same time as another person? Merging two forms together when branching from source control?
That is a source control issue - not the product itself. Common really, there is a difference.
Yes, that is true. If you are using .Net however the problem is easier to handle.
We have a Source Control administrator team (full time positions...source/version control is all they do - sounds really dull :sick: ), and they handle all of the stuff. I have had issues checking code in and out, but not a whole lot. The source and version control aspects are all handled out of our Texas office.Quote:
Originally Posted by Grimfort
I am in a small team of 5, and I design, code, manage source control and even check documentation. Lucky ole you to dodge that bullet :).
Hack, where do you work? Adobe, Microsoft, Symantec? :D