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
  #61  
Old 03-28-2005, 05:18 AM
brandnew's Avatar
brandnew brandnew is offline
Centurion
 
Join Date: Jun 2004
Location: Phnom Penh, Cambodia.
Posts: 181
Default


Oh, playing math?

VB.net = Visual Basic Syntax + .Net Framework
.Net Framework = Full OOP + ASP.Net ++++

=> VB.net = Visual Basic Syntax + Full OOP + ASP.Net ++++
__________________
Very useful and free stuffs for VB programmers.
API-Guide - Wonderful API viewer with examples and full explanation.
APIViewer - More APIs; replacement for default api viewer in VB.
Reply With Quote
  #62  
Old 06-15-2005, 10:56 AM
whaase whaase is offline
Newcomer
 
Join Date: Jun 2005
Posts: 3
Default

What would you start with if you have never programmed before and want to learn? VB6 or VB.Net? If price didn't matter.

Walter
Reply With Quote
  #63  
Old 06-15-2005, 11:27 AM
John's Avatar
John John is offline
Bit Flipper
 
Join Date: Feb 2002
Location: The Inner Loop
Posts: 5,550
Default

VB.NET, hands down. You can't even buy VB6 anymore unless you get it from eBay or have an MSDN subscription.
__________________
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
  #64  
Old 07-05-2005, 09:53 AM
elnerdo's Avatar
elnerdo elnerdo is offline
Contributor
 
Join Date: Jul 2004
Location: Northern New Jersey
Posts: 490
Default

Does vb6 have option strict?
__________________
nerds unite!
Reply With Quote
  #65  
Old 07-05-2005, 10:43 AM
Flyguy's Avatar
FlyguyThe Official VB6 vs VB.NET Thread Flyguy is offline
Lost Soul

Super Moderator
* Guru *
 
Join Date: May 2001
Location: Vorlon
Posts: 19,164
Default

No.
Reply With Quote
  #66  
Old 08-01-2005, 05:25 AM
crabby's Avatar
crabbyThe Official VB6 vs VB.NET Thread crabby is offline
mostly gone

Retired Moderator
* Expert *
 
Join Date: Aug 2002
Location: Oppum / Rhine area
Posts: 2,721
Default

Now for all that need a reason the make 'The Move'. Introducing Visual Basic 2005 for Developers is a free online book from MS, it gave me the final push.
__________________
there are always two sides of a story and 12 ways to sing a song or write some code. so whats wrong ?

Avatar by lebb
Reply With Quote
  #67  
Old 08-13-2005, 03:36 PM
the master's Avatar
the master the master is offline
Tachikoma
 
Join Date: Mar 2003
Location: Mansfield, UK
Posts: 4,596
Default

hi, i just couldnt help but post in this thread.

ive tried both VB6 and VB.NET. ok, ive spent like 5 years in VB6 and ive only tested .net out a bit so it might not be a fair judgment. ive also tested #develop and visual studio.net. i didnt seem to get very far with anything to do with .net. the first thing i thought i would try was a simple screensaver with some shapes. OH NO! wheres the circle and line commands gone! something that simple takes a lot of code now with dimming pens and colors and shapes and things.

how about loading a form? ive still not managed to load a second form through code. (not really tried but it looks complicated)

ok, .net has some nice things about it. when drawing a shape you can draw a rounded rectangle. looks good but also takes a lot more code.

heres a nice one. winsock! does this exist anymore? last i heard it was about 50 lines of code to replace "winsock1.connect"

.net isnt anything like vb6. it is completely different. i dont have a problem with different languages but Micro$oft is trying to replace VB6 with VB.net. its like saying "lets get rid of html and replace with C++"

after running a few tests between the few ive decided that .net is stupidly slow. ok, i was testing on a slowish PC but VB6 can cope fine with it.

the IDE is harder to use. its like using the C++6.0 IDE. the code even resembles C++ more than it does VB. at first i thought it would be good to move to a newer language. afterall, i like new things. ive upgraded through most versions of windows and liked each one more than the last. with the possible exception of windows ME. the trouble with .net is that its completely different and trying to replace something asif its a little upgrade. im not happy with wasting a few years getting good at a language only to find out that Micro$oft wants to kill it. ill buy visual studio.net and 2 months later there will be something new out that looks more like assembly code.

so, VB.net can do a lot more than VB6. hmm, it might be able to. but its harder to work with and i cant think of much where the extra controll over things and extra functions would be of much benefit. drawing a circle. why does it take loads of code for it? its a simple task, why not have 1 simple line of code?

i would also like to know what this upgrader is. has anyone ever successfully upgraded any code?

i dont think its worth the trouble using .net for the amount of benefits it gives. it is ofcourse just another way for Micro$oft to make money. im sticking with VB6. once VB6 is unusable im sure someone will make an emulator for it which im sure will still run loads faster than .net. when its completely gone then im moving to html/php (if there still arround) and doing web stuff.

personally i think it wouldnt be too bad if VB6 and .net lived together. best of both worlds, everyones happy. a lot of ppl wanna stick with VB6 and a lot of ppl like .net. they are both existing at the same time now. why not keep it like that
__________________
"That which seems simple is often overlooked" ~ me
Halloween 2014 Yard Haunt
Halloween Special FX
Reply With Quote
  #68  
Old 08-14-2005, 12:08 AM
by_m's Avatar
by_m by_m is offline
Contributor
 
Join Date: Jul 2004
Location: Texas
Posts: 661
Default

To learn new things you have to start out with the mindset of wanting to learn, being willing to try hard to learn something new.
OK, I had it easy, I started learning VB6 in 2002, but then .Net came and I never finished, I switched having scarely started. I didn't find it hard because my goal was to learn, I was willing to try, and I had a fresh start.
I could go on now to tell you that the graphics aren't really that hard and I can demonstrate how simple it is in .net, but you still wouldn't be convinced. I could point out many things that were greatly blown out of proportion in what you just wrote, but it wouldn't make a difference.
You already decided that VB.net is evil, but you obviously haven't even begun to learn from a fresh point of view, which is something that takes a little effort. Your point is that VB.net is incredibly complicated, you said that it and VB6 are like html and C++. That statement right there shows that you are going into it from a VB6 perspective instead of one open to learning new things.
What happens if you are a VB6 developer trying to open a new form in VB.net? Well, in this case, it sounds like you tried to do it like you would in VB6 and decided that it's difficult and complicated. What do I do as someone who hasn't used VB6? I spend a couple minutes on the forum and come up with some very simple (and I may add, very logical) code that works perfectly fine. It really is a difference in perspective.
But honestly, even if it were the simplest thing on earth, why would you want to do it? Well, why don't you look into it? Aside from the fact that VB.net is the future and that almost nothing can change that, with an open and positive mind look into the benefits of VB.net. Look into what good is being said about VB.net and ask yourself (or see for yourself) if it's true. After you do that, see if it's worth switching for the benefits. If not, stick with VB6, like you said, someone will come up with an emulator for it. If you see that there just may be some good things in VB.net, then start again and try to learn it with a fresh mind. People have done it, and they have said it's a good change. Honestly, if you really put some effort into seeing how it's done and not just get upset about how typing in stuff from VB6 doesn't work anymore, you can learn it.
Simply put, VB.net is the future, and the only difficulty is in giving it your all. If nothing else you may just want to learn it because it will help you to expand your horizons a bit. Why stay stuck on any language? If it's because you think that a certain other one is too difficult, too stupid, or maybe both, then realize that if it really was that way then no one would want to use it. I will state for my part that VB.net is not difficult and that VB.net works. I think that I am not alone...
__________________
170 10101010 410 J31^170
Reply With Quote
  #69  
Old 08-14-2005, 05:44 AM
the master's Avatar
the master the master is offline
Tachikoma
 
Join Date: Mar 2003
Location: Mansfield, UK
Posts: 4,596
Default

ok, maby i was being a bit hyperbolic but i did go into .net and want to learn how it works and see the new features but i was greatly put off mainly by how simple things in VB6 are now more complicated. i suppose when you know how then its not so hard but its still more code. yes i see that .net has benefits. a few things i like are how easy tray icons are and making parts of a form transparent. things that i can do in VB6 but VB6 is a lot harder for these.

i dont mind learning a new language. before i knew anything about programming i found myself a C++ book and tried to read it but i couldnt figure anything out. i didnt have anything to write and test the code with so that didnt help. then i got visual studio 6 and found VB6. within 2 hours i knew how to use a lot of the simple things like if-then's and loops etc.

since learning VB6 i have learned html, javascript, php and now im working on C++ again which seems so simple after knowing VB and php. i heard C++.net is almost exactly the same as C++6 so that sounds like a good language to learn. i wouldnt mind doing graphic type programs like 3D games so C++ would probly be the best.

i havnt thrown .net in he bin. from time to time i do still go and look at it and really wanna learn how it works but not long after starting i get put off again
__________________
"That which seems simple is often overlooked" ~ me
Halloween 2014 Yard Haunt
Halloween Special FX
Reply With Quote
  #70  
Old 08-15-2005, 03:37 AM
crabby's Avatar
crabbyThe Official VB6 vs VB.NET Thread crabby is offline
mostly gone

Retired Moderator
* Expert *
 
Join Date: Aug 2002
Location: Oppum / Rhine area
Posts: 2,721
Default

If you really want to learn than uninstall VB6 and stop whining about how difficult VB.NET is. VB.NET is a different language and has its of advantages over VB6 event though you'll spend a good deal of time on finding the right classes you need but once you start to get familiar with the framework it its actually quite nice. I haven't completely moved away from VB6 but today I hardly use it for new projects, one of the reasons would be its so easy to implement/bind-in webpages (You get away without knowing much HTML/ASP.NET)
__________________
there are always two sides of a story and 12 ways to sing a song or write some code. so whats wrong ?

Avatar by lebb
Reply With Quote
  #71  
Old 08-15-2005, 10:27 PM
brandnew's Avatar
brandnew brandnew is offline
Centurion
 
Join Date: Jun 2004
Location: Phnom Penh, Cambodia.
Posts: 181
Default

themaster, many vb6 programers including me felt the same as you when tried to learn vb.net. I had no intention to throw vb6 away, but after a while with vb.net, I knew I couldn't go back to vb6.

The fact that vb.net is more difficult than vb6 is there are quite a lot of new technologies introduced, kind of tech that pure vb6 programmers never seen before: winforms, multithreading, inheritance, interface, low-level socket, serialization, crypto, ado .net, etc.

My prior approach to learn these great stuffs is read vb.net books and practice along at least 1 month non-stop. I tried to write from a simple hello-world program to a complex 10-project solution and up to 100 projects in a suite. For me, a key to success in vb.net is to say "Those guys can do it. I can do it too! Those guys think it's easy. I'll show them it's much easier for me!"
__________________
Very useful and free stuffs for VB programmers.
API-Guide - Wonderful API viewer with examples and full explanation.
APIViewer - More APIs; replacement for default api viewer in VB.
Reply With Quote
  #72  
Old 08-16-2005, 12:18 AM
the master's Avatar
the master the master is offline
Tachikoma
 
Join Date: Mar 2003
Location: Mansfield, UK
Posts: 4,596
Default

i know i can do it because ive made a nice little screensaver in it at the cost of a few hours work rather than a few minutes (thats after learning the parts i needed to use).

i tried learning C++ years ago and gave up as it was too hard. i since found VB6 and knowing VB6 i just seemed to know lots about C++. obviously i still need to learn more about it but .net looks more like C++ than VB and yet knowing VB6 like english and a nice amount of C++ doesnt seem to help me at all.

one of the biggest problems ive seen though is the speed it runs at and apps hanging. i always test out my programs on a really crap PC, if they work on that they will work on anything. .net apps dont seem to. simply dragging a window causes the form to flash a bit and cut the side off for half a second. and when making a simple do-loop, the appa decided to crash. yes i was using application.doevents

i think what ill do is install #develop when my new network goes up (alongside VB6). i dont seem to use VB much now at all as the main project i had going was my webserver which ive decided to replace with apache. i will probly look at C++.net too. how different is that? if thats anything similar to C++6 then ill probs use that for the game i wanna start
__________________
"That which seems simple is often overlooked" ~ me
Halloween 2014 Yard Haunt
Halloween Special FX
Reply With Quote
  #73  
Old 08-16-2005, 11:01 AM
brandnew's Avatar
brandnew brandnew is offline
Centurion
 
Join Date: Jun 2004
Location: Phnom Penh, Cambodia.
Posts: 181
Default

Is #develop crashed right? This tool crashes 9 out of 10 times when I code in vb.net even on fast pc. It has bugs!

It's obvious that .net program cannot just crash and die. Maybe the app threw an exception, and you hadn't coded exception handling. Use try..catch or try...catch...finally blocks to catch unhandled exceptions. Learn to kill exceptions.

If you miss vb6's winsock control a lot, you can use a clone one. Search the net for it. There're also shape controls clone for vb.net.
__________________
Very useful and free stuffs for VB programmers.
API-Guide - Wonderful API viewer with examples and full explanation.
APIViewer - More APIs; replacement for default api viewer in VB.
Reply With Quote
  #74  
Old 08-16-2005, 11:03 AM
the master's Avatar
the master the master is offline
Tachikoma
 
Join Date: Mar 2003
Location: Mansfield, UK
Posts: 4,596
Default

lol, i prefer #develop actually and when i made that i was testing the proper Micro$oft IDE. i know someone who was gonna make me a winsock control... if i ever get round to needing one. most of my time is taken up by php and html now
__________________
"That which seems simple is often overlooked" ~ me
Halloween 2014 Yard Haunt
Halloween Special FX
Reply With Quote
  #75  
Old 08-16-2005, 11:19 PM
DominusMegadeum DominusMegadeum is offline
Regular
 
Join Date: Jun 2005
Posts: 57
Default Why give up VB6 at all?

If you're comfortable with it you can ease the transition to VB.NET by using some .NET classes in your VB6 progs: http://msdn.microsoft.com/vbrun/vbfusion/default.aspx

You DON'T need VB/VS.NET, just the .NET Framework.
Reply With Quote
  #76  
Old 08-17-2005, 12:11 AM
the master's Avatar
the master the master is offline
Tachikoma
 
Join Date: Mar 2003
Location: Mansfield, UK
Posts: 4,596
Default

haha, cool. i quite like the idea of that. just a thought tho. is this VB6 or .net code?
Dim fso As Scripting.FileSystemObject
Set fso = New Scripting.FileSystemObject

it looks like VB6 with a reference setup but it never said about referencing it so im assuming its .net style??
__________________
"That which seems simple is often overlooked" ~ me
Halloween 2014 Yard Haunt
Halloween Special FX
Reply With Quote
  #77  
Old 08-17-2005, 01:01 AM
brandnew's Avatar
brandnew brandnew is offline
Centurion
 
Join Date: Jun 2004
Location: Phnom Penh, Cambodia.
Posts: 181
Default

It's definitely vb6 code. VB.net uses better IO classes of .net framework to do FSO jobs, and if same code is in vb.net, the it would be:

Dim fso As Scripting.FileSystemObject
fso = New Scripting.FileSystemObject

or

Dim fso As Scripting.FileSystemObject = New Scripting.FileSystemObject

or

Dim fso As new Scripting.FileSystemObject
__________________
Very useful and free stuffs for VB programmers.
API-Guide - Wonderful API viewer with examples and full explanation.
APIViewer - More APIs; replacement for default api viewer in VB.
Reply With Quote
  #78  
Old 08-17-2005, 02:51 AM
the master's Avatar
the master the master is offline
Tachikoma
 
Join Date: Mar 2003
Location: Mansfield, UK
Posts: 4,596
Default

hmm, seems simple enough. so, are most things accessible in the same way? like when i load the FSO object, rather than add it in references i load it at runtime so i can catch any errors with loading it without my app breaking (applies to most things like this).

the way i usually load it is

set FSO=createobject("Scripting.Filesystemobject")

if i loaded something else that was like createobject("somedllname.someclass"). would it just be the same in .net without the createobject()? or is it just coincidence that filesystemobject is the same?
__________________
"That which seems simple is often overlooked" ~ me
Halloween 2014 Yard Haunt
Halloween Special FX
Reply With Quote
  #79  
Old 08-17-2005, 07:38 AM
reboot's Avatar
rebootThe Official VB6 vs VB.NET Thread reboot is offline
Keeper of foo

Retired Moderator
* Guru *
 
Join Date: Nov 2001
Location: Graceland
Posts: 15,614
Default

There is no point in using FSO in .net. File IO is built in.
__________________
~ Quod non mortiferum, fortiorem me facit ~

Avatar by lebb
Reply With Quote
  #80  
Old 08-20-2005, 03:48 AM
Mathimagics's Avatar
MathimagicsThe Official VB6 vs VB.NET Thread Mathimagics is offline
Algorithms 'R' Us

Forum Leader
* Guru *
 
Join Date: Jun 2002
Location: Canberra
Posts: 4,159
Default Battle of Languages and the API War

I've only just come across this article, it's a year old but well worth a read:

How Microsoft Lost the API War (Joel on Software, June, 2004)

He's discussing the impact and consequences of MS's API and OS strategies, and that makes interesting reading, but of particular interest to me were the comments towards the end of the article ("Oh Wait, There's More Coming", "It's not 1990!" and "Enter the Web").

For example, his company's reasons for not porting their major VB6 apps to .NET ("there's no return on [ time ] investment for us"), and his general comments on client applications vs web applications (i.e. they are essentially different, and a language that's good at one isn't necessarily the way forward for the other).

These more or less echo my own reasons for eschewing (at last, an opportunity to deploy that word in a VB tech forum!) .NET, it's not that I'm a luddite (not, at least, on this issue), it's simply that my programming is entirely concerned with client applications, not web-based or web-enabled apps, and so, like Joel, moving to VB.NET seems a very counter-productive move, esoteric considerations regarding whether it's "more OO" notwithstanding.


Dr Memory
VB6 Fortress of Solitude
20 Aug 2005

PS: Our calculations (on a nuclear-powered parallel abacus) suggest that both of the following events are probably going to occur before VB6 becomes a genuinely "legacy" SDK, regardless of its official status:
  • the peaking of the world's total oil production
  • the (already obvious) thawing of the Siberian permafrost reaching the "catastrophic" stage

They WILL all happen, of course, but the smart money is now shifting to the permafrost option!

__________________
Cogito, ergo codo
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
 
-->