The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
Go Back  Xtreme Visual Basic Talk > > > The Official VB6 vs VB.NET Thread


Reply
 
Thread Tools Display Modes
  #1  
Old 01-12-2005, 10:38 AM
HardCode's Avatar
HardCodeThe Official VB6 vs VB.NET Thread HardCode is offline
Ultimate Contributor

Forum Leader
* Expert *
 
Join Date: Feb 2004
Location: New Jersey
Posts: 3,339
Default The Official VB6 vs VB.NET Thread


Welcome. Please use this thread to freely pose your questions and discuss your views about differences, upgrading, and converting from VB6 to VB.NET.

Please note: This thread is not for personal likes or dislikes about the differences of VB6 and VB.NET, rather for discussions of a more technical nature that will help readers make a more informed opinion about the two software products if they are trying to decide between the two. Information about the pros and cons to help readers determine if they should upgrade now, wait until the next project, continue maintaining existing code without changing, etc (and why), is what this is all about.

Also note that this thread is not for questions regarding changes in syntax from VB6 to VB.NET.

Posts out of context will promptly be removed by our fine moderating staff
__________________
DON'T CLICK HERE

Useful forum tags: [VB][/VB], [CODE][/CODE], [HTML][/HTML]

Last edited by HardCode; 01-27-2005 at 02:36 PM.
Reply With Quote
  #2  
Old 01-16-2005, 04:21 PM
wicko3's Avatar
wicko3 wicko3 is offline
Junior Contributor
 
Join Date: Dec 2003
Location: England
Posts: 254
Default

How long is VB6 going to be around d'ya think? How long until everything is .Net?
__________________
Error - keyboard not detected. Press F1 to continue.
Reply With Quote
  #3  
Old 01-17-2005, 09:15 AM
HardCode's Avatar
HardCodeThe Official VB6 vs VB.NET Thread HardCode is offline
Ultimate Contributor

Forum Leader
* Expert *
 
Join Date: Feb 2004
Location: New Jersey
Posts: 3,339
Default

Officially, VB6 is no longer around, since you cannot purchase it directly from Microsoft anymore. The only way to buy it is from someplace like eBay, or from a software retailer that happens to still have a copy for sale. That said, I believe that the day Microsoft replaces VBA in Office with .NET, then many more companies will completely phase out VB6/VBA for any new projects. It all depends on the needs of the entity sponsoring the program. Some DOS programs are "still around," simply because they still work for their given function. No programming language will ever disappear, because there will always still be enthusiasts that keep them alive. Support from Microsoft, on the other hand, is a completely different matter
__________________
DON'T CLICK HERE

Useful forum tags: [VB][/VB], [CODE][/CODE], [HTML][/HTML]
Reply With Quote
  #4  
Old 01-18-2005, 02:05 AM
Himo Himo is offline
Junior Contributor
 
Join Date: Oct 2003
Location: Weert, The netherlands
Posts: 288
Default

I think to have heard all support from microsoft will be seized at the end of 2008-2010. So that should be the end of it. I think if Microsoft really wants to push .NET, they just make everything CLR compliant, thus rendering older languages useless.(e.g. changing the kernel, removing the registry, changing memory management)
__________________
For questions about VS .net extensibility, please fire at me! :)
For readability, please use the [vb][/vb] tags
Reply With Quote
  #5  
Old 01-18-2005, 12:04 PM
wicko3's Avatar
wicko3 wicko3 is offline
Junior Contributor
 
Join Date: Dec 2003
Location: England
Posts: 254
Default

Is VB.NET compiled or something? Because when I tried it (once) at school, it took a good few seconds to start the program after I clicked 'Run'.

Also, what do people think of the way it indents your code for you? As I've said, I've only tried VB.NET once, but I'm guessing that the auto-indent feature loses you some freedom in the layout of your code. (Like if you wanted to make a pretty pattern down the left edge of your code!) Then again, I suppose you could turn auto-indent off.
__________________
Error - keyboard not detected. Press F1 to continue.
Reply With Quote
  #6  
Old 01-18-2005, 05:41 PM
Toveling's Avatar
Toveling Toveling is offline
Contributor
 
Join Date: Oct 2003
Posts: 417
Default

Quote:
Originally Posted by wicko3
Is VB.NET compiled or something? Because when I tried it (once) at school, it took a good few seconds to start the program after I clicked 'Run'.
.NET programs compiles to the .NET Common Intermediate Language.

Quote:
Also, what do people think of the way it indents your code for you? As I've said, I've only tried VB.NET once, but I'm guessing that the auto-indent feature loses you some freedom in the layout of your code. (Like if you wanted to make a pretty pattern down the left edge of your code!) Then again, I suppose you could turn auto-indent off.
And you cant join code obfusication contests and make pretty picures ..

I think it's nice.. But for some things that used to be extreamly easy tasks in VB6, it's a lot more complex in VB.NET.. Nice if you're making a full product, but not needed if you're making a small tool for personal use.
Reply With Quote
  #7  
Old 01-19-2005, 09:14 AM
ReadError's Avatar
ReadError ReadError is offline
Junior Contributor
 
Join Date: Nov 2003
Location: Québec city, Canada
Posts: 310
Default

Quote:
Originally Posted by wicko3
Is VB.NET compiled or something? Because when I tried it (once) at school, it took a good few seconds to start the program after I clicked 'Run'.
In .NET, programs are compiled to exe before being run. I'm sure in VB6 you already saw a program acting differently running from IDE or exe. That's why they changed it.
__________________
Use the [vb][/vb] tags!!
If you don't use Option Explicit in your code, don't complain if it doesn't work.
Reply With Quote
  #8  
Old 01-26-2005, 06:43 PM
Turiya's Avatar
Turiya Turiya is offline
Contributor
 
Join Date: Oct 2004
Location: Calgary, Alberta, Canada
Posts: 555
Default Is VB.Net worth it?

I own VB6, is VB.NET worth the money? I use VB about three times a week.
Reply With Quote
  #9  
Old 01-27-2005, 04:12 AM
Faith's Avatar
Faith Faith is offline
Contributor
 
Join Date: Sep 2003
Location: Finland
Posts: 690
Default

Objectively: Yes
__________________
I love deadlines. I like the whooshing sound they make as they fly by. - Douglas Adams
Reply With Quote
  #10  
Old 01-27-2005, 08:41 AM
Gurduloo Gurduloo is offline
Newcomer
 
Join Date: Oct 2003
Posts: 11
Default

If you use VB three times a week, then definately yes. I only use it about once a month and I'm glad I upgraded to .NET. Many improvements have been made.
Reply With Quote
  #11  
Old 01-27-2005, 09:19 AM
AtmaWeapon's Avatar
AtmaWeaponThe Official VB6 vs VB.NET Thread AtmaWeapon is offline
Fabulous Florist

Forum Leader
* Guru *
 
Join Date: Feb 2004
Location: Austin, TX
Posts: 9,500
Default

It depends on if you are programming for yourself or with the goal of eventually having a career.

If you are coding just for yourself, there may be no reason to go and buy VB .NET. If you are good with VB6 and it does all you want, then it is the right tool for the job. Of course, getting .NET couldn't hurt, but there's no need to go spending money if what you have is doing the job.

However, if you are looking for a career, it would be best to start looking at .NET. Microsoft won't let itself be forced to support VB6 forever, and I'm not certain VB6 apps will work on Longhorn (though that is a guess I cannot support with a valid source so please don't take that as a fact). VB6 is by no means a dead language, but Microsoft is doing its best to kill it. Within a few years, there will be more .NET programmers than VB6 programmers, and VB6 jobs will begin to be limited to maintaining legacy projects.

In both cases, though, I recommend waiting until later this year to purchase Visual Studio .NET. Visual Studio 2005 is due sometime this year, and it is a very big improvement over Visual Studio 2003. It would be aggravating to drop $100 or so on a program and have the new version come out in a couple of months, so for right now it might be best to pick up the beta version from here. It's near fully functional and dead sexy so I say give it a whirl if you are interested.
__________________
.NET Resources
My FAQ threads | Tutor's Corner | Code Library
I would bet money 2/3 of .NET questions are already answered in one of these three places.
Reply With Quote
  #12  
Old 01-27-2005, 09:33 AM
DJ_Klepc's Avatar
DJ_Klepc DJ_Klepc is offline
Contributor
 
Join Date: Apr 2004
Location: Slovenia
Posts: 602
Default

I hate VB.NET!!!

To much changes (VB6->VB.NET)

There is no Control Arrays and so on....

You can't start new project without saving it. (i think)
__________________
DJ_Klepc
Reply With Quote
  #13  
Old 01-27-2005, 09:37 AM
Faith's Avatar
Faith Faith is offline
Contributor
 
Join Date: Sep 2003
Location: Finland
Posts: 690
Default

Then again, control arrays can SO be done, and I see nothing bad in projects being saved when they are started...
__________________
I love deadlines. I like the whooshing sound they make as they fly by. - Douglas Adams
Reply With Quote
  #14  
Old 01-27-2005, 10:05 AM
wayneph's Avatar
waynephThe Official VB6 vs VB.NET Thread wayneph is offline
Web Junkie

Retired Moderator
* Expert *
 
Join Date: Apr 2004
Location: D/FW, Texas, USA
Posts: 8,393
Default

And when 2005 comes, you're no longer forced to create a project at start up, and brings back edit and continue.
__________________
-- wayne, MSSM Retired
> SELECT * FROM users WHERE clue > 0
0 rows returned
Reply With Quote
  #15  
Old 01-27-2005, 11:13 AM
Mike Rosenblum's Avatar
Mike Rosenblum Mike Rosenblum is offline
Microsoft Excel MVP

Forum Leader
* Guru *
 
Join Date: Jul 2003
Location: New York, NY, USA
Posts: 7,848
Default

Quote:
Originally Posted by DJ_Klepc
I hate VB.NET!!!
To much changes (VB6->VB.NET)
There is no Control Arrays and so on....
You can't start new project without saving it.
VB.Net is a lot to get your head around. I've been doing it 2 mos. solid and I still can't do some of the basics, but I'm getting there...

But the parts I've learned already are clearly so superior there is no doubt which direction to go in. For what it's worth, I jumped into .Net after Thanksgiving, determined to "get it", having been rebuffed in my efforts a couple of times previously. After 7 days of solid reading, studying and experimenting, I was sweating bullets and getting nowhere. After 10 days the same, just with a massive head-ache. I almost gave up -- again.

But on the 11th day, I don't know, something clicked. Mind you I was putting in 12hr+ days so, we're talking about 120+ hrs of solid studying before I started to feel comfortable at all. (Not any good, but at least starting to see the big picture.) If one is not strong at OOP, then .Net will be even harder to get your head around. On the other hand, if you are less dense than I am, you might find it a lot easier.

Bottom line: be patient. Stick with VB6 until you are comfortable enough with VB.Net. In the mean time, get a good VB.Net book and read it over time. Eventually it will start to sink in.
__________________
My Articles:
| Excel from .NET | Excel RibbonX using VBA | Excel from VB6 | CVErr in .NET | MVP |
Avatar by Lebb

Last edited by Mike Rosenblum; 01-27-2005 at 02:29 PM.
Reply With Quote
  #16  
Old 01-27-2005, 10:59 PM
zelg37The Official VB6 vs VB.NET Thread zelg37 is offline
Contributor

* Expert *
 
Join Date: Dec 2004
Location: Oregon, USA
Posts: 606
Default Decompilation of Managed .Net Code

I'm still waiting to make the jump from VB6 to .Net, but one concern I had (probably unfounded, but it does come up in some of the research I've done).

What about the issue of decompilation and protection of source code? I know it's a pretty non-trivial task to decompile a natively compiled VB6 exe (although I guess not impossible - VBRB), but what about managed code under .Net?

I know that for VB.Net and C#.Net you have to use managed code, while C++ you have a choice of managed or unmanaged code. It seems like managed code is pretty easy to decompile unless you use obfuscators. Is writing unmanaged C++ code in the .Net framework better than obfuscated VB.Net code in terms of resisting decompilation?

Also, I know there's a speed-of-development trade-off as well as an increased chance of memory issues with the unmanaged C++ code, but maybe more opportunities for optimization. I've also heard the garbage collection using managed .Net code is best described as a "work-in-progress", but there are workarounds not to have to depend on it too much...

Anyway, just wanted to throw those out (because they weren't coming up), just to see if anyone else considers them serious tech issues with the .Net framework.

Is anyone out there using (or tried) Mono? Does it have any advantages over Visual Studio.Net?

Oh..and what's stiopping from making the jump?
I guess the faint hope that Microsoft will come out with a decent (near 100%) robust conversion tool from VB6 to VB.Net. (Yeah I know I dreaming, but...)
Reply With Quote
  #17  
Old 01-28-2005, 07:14 AM
John's Avatar
John John is offline
Bit Flipper
 
Join Date: Feb 2002
Location: The Inner Loop
Posts: 5,550
Default

When you use C++.NET to write unmanaged code you are doing the same thing you would be doing with any other non .NET compiler including VC++6, gcc etc.

Just to clear things up a little bit here disassembly and decompilation are two very different things. Decompilation means you take the bits and bytes and turn it into the original source code. Disassembly is when you take the bits and bytes and turn it into an ASM listing or ASM source. Disassembly is far easier than decompilation.

As far as I know, about the only thing you can do to protect your code in .NET is to use the obfuscators, as you mentioned, since .NET comes with a nice disassembler out of the box (ILDASM.EXE).
__________________
Subclassing|Magnetic Forms|Operator Overloading (VB2K5)|QuickSnip.NET

"These Patriot playoff wins are like Ray Charles songs, Nantucket sunsets, and hot fudge sundaes. Each one is better than the last." - Dan Shaughnessy
Reply With Quote
  #18  
Old 02-03-2005, 12:54 PM
rex64 rex64 is offline
Senior Contributor
 
Join Date: Jul 2003
Posts: 1,171
Default program VB6 in VB.Net

I was wondering if I can make VB6 programs for VB.NET?

Or (I am not tring to sound mad), is .NET compltiable with 200 other languages, but not Microsoft's own VB6. Lol.

Also, if I program in VB6 from .NET can I tell it to not output to framwork?
Reply With Quote
  #19  
Old 02-03-2005, 01:05 PM
esposito's Avatar
esposito esposito is offline
Contributor
 
Join Date: Jul 2003
Location: Perugia - Italy
Posts: 456
Default

VB6 and VB.NET are two completely different languages.

There's little compatibility between the two. The former produces unmanaged code, the latter managed code that requires the .NET Framework to work.

Quote:
Originally Posted by rex64
I was wondering if I can make VB6 programs for VB.NET?

Or (I am not tring to sound mad), is .NET compltiable with 200 other languages, but not Microsoft's own VB6. Lol.

Also, if I program in VB6 from .NET can I tell it to not output to framwork?
Reply With Quote
  #20  
Old 02-03-2005, 01:06 PM
rex64 rex64 is offline
Senior Contributor
 
Join Date: Jul 2003
Posts: 1,171
Default managed code

What is managed code?
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Forum Jump

Advertisement:





Free Publications
The ASP.NET 2.0 Anthology
101 Essential Tips, Tricks & Hacks - Free 156 Page Preview. Learn the most practical features and best approaches for ASP.NET.
subscribe
Programmers Heaven C# School Book -Free 338 Page eBook
The Programmers Heaven C# School book covers the .NET framework and the C# language.
subscribe
Build Your Own ASP.NET 3.5 Web Site Using C# & VB, 3rd Edition - Free 219 Page Preview!
This comprehensive step-by-step guide will help get your database-driven ASP.NET web site up and running in no time..
subscribe
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
 
The Official VB6 vs VB.NET Thread
The Official VB6 vs VB.NET Thread
 
-->