.NET [modified]
-
I've been reading over alot of .NET code(VB) and so far I don't like what I see. I hate being behind in times but I'm wondering is it worth switching from vb6 to .NET? Whats so good about .NET? P.S. if you're just going to be a jackass then please don't answer. I would like some serious replies. -- modified at 16:00 Wednesday 28th March, 2007
Stigmurder wrote:
I hate being behind in times but I'm wondering is it worth switching from vb6 to .NET? Whats so good about .NET?
It's slightly less of a heap of bizarre syntax bolt-ons, compatibility hacks, and hidden sub-systems than VB6. More importantly, once you have your code in VB.NET you can convert it fairly easily to C#, which will demonstrate clearly just how twisted the VB stuff was. And by the way - this is a serious reply. I used BASIC then QBasic for years. Before starting my current job, i had roughly equal amounts of C++ and VB experience. And of the four languages i use every week, VB.NET is currently at #2 or #3. VB (with or without .NET... but especially without) is a hack-job, pure and simple. I respect folks that have become bona-fide experts in the usage and idiosyncrasies of it, the same way i respect the folks who write DHTML flight simulators, or statistical analysis in SQL... but it's still a mess, and the sooner you toss it to the curb the better off you'll be.
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
I've been reading over alot of .NET code(VB) and so far I don't like what I see. I hate being behind in times but I'm wondering is it worth switching from vb6 to .NET? Whats so good about .NET? P.S. if you're just going to be a jackass then please don't answer. I would like some serious replies. -- modified at 16:00 Wednesday 28th March, 2007
I'm going to run and hide from this thread... But being seriously, it's amazing what more you can do with .NET. You really can't cover it in a post. A lot of people here hate VB period (I am not a huge fan but I don't hate it) and might say that vb.net isn't going to do anything, try c#.net etc. If nothing else, it's just plain cool to play around with!
_________________________________________ You can't fix stupid, but you can medicate crazy.
-
I'm going to run and hide from this thread... But being seriously, it's amazing what more you can do with .NET. You really can't cover it in a post. A lot of people here hate VB period (I am not a huge fan but I don't hate it) and might say that vb.net isn't going to do anything, try c#.net etc. If nothing else, it's just plain cool to play around with!
_________________________________________ You can't fix stupid, but you can medicate crazy.
hate vb? geez. I guess even programmers can be stuck up.
-
hate vb? geez. I guess even programmers can be stuck up.
Stigmurder wrote:
I guess even programmers can be stuck up.
It's not about being stuck-up. Well, ok, that's some of it - if you've ever worked with someone who was stuck on a single tool and bad at using even that, then you're gonna take a rather dim view of it. Prejudice has its purpose... But yeah, personally it isn't about "hating on the VBer" so much as it's something i've used and don't care for. I also hate mucking out cattle pens, but don't think i'm "too good" for it (i'd just rather do almost anything else...)
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
It just seems like more work to write a prog in .NET. But then again I really don't know. Thats why I'm asking. I'll go look for some examples.
Stigmurder wrote:
It just seems like more work to write a prog in .NET.
I think it depends. There's lots of things that are much easier to do in .NET, until you want to do something the .NET API doesn't support, then it's a PITA. Of course, I get the impression you're probably looking at code that the designer generated, which of course looks gadawful. Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
I've been reading over alot of .NET code(VB) and so far I don't like what I see. I hate being behind in times but I'm wondering is it worth switching from vb6 to .NET? Whats so good about .NET? P.S. if you're just going to be a jackass then please don't answer. I would like some serious replies. -- modified at 16:00 Wednesday 28th March, 2007
Hi. I never seriously worked with visual basic so I cant say that this or that is better compared to that language but the thing I can say about C#.Net is that it works good and covers a wide area of development from stand alone desktop applications to asp.net driven websites, that (if made smaller) are perfect to be viewed on a mobile phone, or desktop applications that function (with some work) on mobile PDA devices etc. etc. So I would say that the great diversity of options you have as an developer are great. When you are happy as an hobby programmer with writing your programs in Visual Basic there is nothing wrong with working with that development software, but when you ask what's so good about .Net I personally think this is the answer I have to your question.
With friendly greetings,:) Eric Goedhart Interbritt
-
You know I asked this question with the intent on getting some helpful answers, not to get flamed. Gotta love this vb community.
If you're a VB developer you should be surprised not to get flamed. Many here can't resist taking pot shots at it.
Kevin
-
I've been reading over alot of .NET code(VB) and so far I don't like what I see. I hate being behind in times but I'm wondering is it worth switching from vb6 to .NET? Whats so good about .NET? P.S. if you're just going to be a jackass then please don't answer. I would like some serious replies. -- modified at 16:00 Wednesday 28th March, 2007
Move to VB.NET or C#. You get a better base class library (the .NET framework), a better framework overall, and a better language, and a better IDE and tools. There's still plenty of VB6 out thre but the future is VB.NET
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
It just seems like more work to write a prog in .NET. But then again I really don't know. Thats why I'm asking. I'll go look for some examples.
It's seriously less work, but if you're going to make the effort to switch, do yourself a favour and switch to C#. It's a new, cleaner, language that doesn't suffer from all the legacy idiosyncrasies of VB6, not to mention VB.NET. All you'll lose is exception filtering, which you don't have in VB6 anyway.
-
I've been reading over alot of .NET code(VB) and so far I don't like what I see. I hate being behind in times but I'm wondering is it worth switching from vb6 to .NET? Whats so good about .NET? P.S. if you're just going to be a jackass then please don't answer. I would like some serious replies. -- modified at 16:00 Wednesday 28th March, 2007
As I am sure you know, the real answer to any "what is the best programming language" type question is "it depends on what you want to achieve". For hobby programming, VB6 is fine. If you are doing work for yourself, you might as well work with what you enjoy. For 'serious' work, VB.Net (or C#) are the way to go. The main reason, IMHO, is that VB6 is dead from Microsoft's point of view. Gradually, all the VB6 sites will disappear and the community will dwindle. Increasingly, you will be left behind the rest of the world. You will be unable to interface with the latest technologies and methodologies. There will be nobody left to work with, nobody left to talk to, nobody to appreciate your genius, nobody to maintain your code after you are gone. Of course, all this *could* be an advantage, depending on your personality. There are still COBOL programmers out there who make a good living working on legacy code. Personally, I made the switch to VB.Net from VB two years ago. I love it; not least because of the Visual Studio IDE. IMO, It is a truly remarkable piece of work. I hope this helps. KramII[^]