What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB?
What's the future hold for VB? What's the future hold for VB?
What's the future hold for VB?
Go Back  Xtreme Visual Basic Talk > > > What's the future hold for VB?


Closed Thread
 
Thread Tools Display Modes
  #1  
Old 04-20-2002, 12:40 PM
Ashington Sid
Guest
 
Posts: n/a
Default What's the future hold for VB?


Hello

I've learnt lots from this site and still consider myself a VB novice (I've only been using it for a year). I've read bits about .NET, sure. But, because I'm not really a programmer per se alot of it passes me by. But I have a question. What does the future hold for VB and how will the use of VB in the future differ from how it's used now (if at all?)?

  #2  
Old 04-20-2002, 12:49 PM
Iceplug's Avatar
IceplugWhat's the future hold for VB? Iceplug is offline
MetaCenturion

Retired Moderator
* Guru *
 
Join Date: Aug 2001
Location: Iowa, USA
Posts: 16,583
Default

Wait... let me get my crystal ball.

I don't know what the future holds for VB. I can see older versions of VB becoming more incompatible with updated Windows in the future (with the release of Windows 2012 or Windows ZY), and updated versions of VB (VB10 or something)
Hopefully, it won't be too um... difficult, and that this site will continue helping the eCommunity - the eCommunity will become knowledgable about VB's new surprises and met expectations. The sun will shine gloriously on our eCommunity!

This is just my 2 cent guessing, though.
I also heard rumors that they are trying to make us obsolete.
__________________

Iceplug, USN
Quadrill 1 Quadrill 2 (full) Quadrill 3 JumpCross .NET Website is ALIVE! - DL Platform Tour for VB.NET! Posting Guidelines Hint: Specify your location in your user cp profile if you want compassion!
  #3  
Old 04-20-2002, 01:18 PM
ChiefRedBull's Avatar
ChiefRedBullWhat's the future hold for VB? ChiefRedBull is offline
ISearchGoogle

Retired Moderator
* Expert *
 
Join Date: May 2001
Location: england
Posts: 6,321
Default

.NET won't take over for a while yet, VB5 and upwards are very powerful development tools, capable of producing apps just as good as any C or C++, just as fast (in most cases) in half the time.

The future is of course .NET, but I dn't expect that will come soon. Ten years, maybe more before VB6 and lower are completely eliminated. It's usage is very different from previous versions.... its almost a whole new syntax to learn, and definintely a new way of doing things. Still, I hear of great ideals from the .NET board...
__________________
Chuck Norris ordered a Big Mac at Burger King, and got one.
  #4  
Old 04-21-2002, 04:57 AM
divil's Avatar
divilWhat's the future hold for VB? divil is offline
Funky Monkey

* Expert *
 
Join Date: Nov 2001
Location: England
Posts: 1,289
Default

I think I read somewhere that VB6 will be supported until 2006 or something, so there's plenty of time yet.
__________________
MVP, C#
Now you see why evil will always triumph - because good is dumb.
Windows Forms and WPF user interface controls
  #5  
Old 04-21-2002, 08:43 AM
Anis's Avatar
Anis Anis is offline
| Coder XXX |

Retired Leader
 
Join Date: Jun 2001
Location: Kuala Lumpur, Malaysia.
Posts: 3,018
Default

The following article, which is from the Internet is a summary of few websites. My friend forwarded it to me in this form.. So, i am posting!.. I found some of the contents of this on this Site

Quote:

VB is a language that had its own spirit and sensibility. It had an ethos for many programmers of getting the job done fast, even if we knew in our heart of hearts that our code was a bit of a hack. Time and again, VB just works, period.

Early samples from Microsoft showed us a new Visual Basic that did not look like at all like Visual Basic code. Well-respected VB gurus of the old school weighed in and pronounced that this new doppelganger wasn't VB at all, but a sort of futuristic, soulless ghost.


To Dot Net or Not to Dot Net, That is the Question...

As we have all heard, Visual Studio.NET was released with great fan-fare this week by Microsoft. Now that we have a release version of the program, the choice which all managers have been dreading has reared it ugly head: Do we migrate our VB 6 applications to VB.NET? No article or person can tell you the answer to this question as it is extremely dependant upon your individual situation and must be assessed on a case by case basis. I am going to attempt to give you some of the benefits and drawbacks of moving to VB.NET from VB 6 and then the choice will be yours.

Due to the fact that the new .NET architecture is a major paradigm shift, this question is magnified beyond the migration from version 5 to version 6. Any code which is going to be migrated over needs to be thoroughly evaluated and regression tested before it is moved to a production environment. Due to the changes in the basic foundation of the VB language, bugs can slip into your code in the strangest places and cause unforeseen errors. Microsoft has attempted to alleviate the problems as much as possible by including a Code Migration Tool, but that is not a complete solution. Once the code has been processed using the Tool, every line of code must be re-examined by hand to ensure that the Tool converted the page properly and to clear up any lines the Tool marked as unable to convert.

BENEFITS OF VB.NET

There are many benefits and improvements incorporated in the VB.NET framework. The first benefit is the vastly improved memory and resource management. The resulting stability improvements are a significant reason to consider converting old code and writing all new applications on the framework. Secondly, is the ability to run VB.NET code on all operating systems in the future (ie. Linux, Macintosh, etc) and reduce or remove your dependence on the Windows operating system. Third, a VB.NET application can possibly gain significant performance improvements by implementing a multi-threaded design over the single threaded design of VB 6. Next, moving to VB.NET ensures continued support from Microsoft into the future. The fact of the matter is that Microsoft is going to stop supporting VB 6 sometime in the future. When that day comes, it will be a definite plus to have all the applications migrated over. To do that, it is necessary to start the process now, since it requires so much forethought and effort. Finally, by moving from VB 6 to VB.Net, it will be possible to leverage the existing skills of Visual Basic Programmers. The learning curve in moving from VB 6 to VB.NET is much less than moving to a new language such as C#.


DRAWBACKS:

Having mentioned the benefits, it is only appropriate to mention the downside of migrating all VB 6 applications to VB.NET. First, the learning curve for any existing VB programmers is going to be huge. Even though the learning curve is less than moving to another language, this is still a major shift in the language and most of the skills and expertise that VB programmers had in January became obsolete on February 13th, 2002. It is going to take a lot of time, training, and effort (read money) to get the entire set of VB programmers up to speed and able to start working on the new set of technologies. Second, once the programmers have ramped up their skill sets to be able to start the migration process, they will need to review and possibly re-code major sections of the application to work on the .Net framework. This will be a serious investment for an old application with a limited life span. Thirdly, if the application won’t benefit from a design change to make the application multi-threaded, it may actually suffer a performance loss. Finally, the .net framework runtime will need to be deployed to every machine which will be running the vb.net application. Until the framework is incorporated in the operating system installation, this will be an obstacle which needs to be crossed.

The following suggestions are based on a Microsoft white paper on preparing your VB 6 code for VB.NET. If you make these changes to your VB 6, the migration wizard will do a better job of converting your code for use with VB.NET.


Declare all your variables

Instead of the Variant data type, use Object.

Instead of the Integer data type, use Short.

Use early-binding, not late-binding, when working with objects.

Use Date for storing dates, not Double as in VB 6.

Specify all properties for components and objects--don't use default properties as they aren't supported in VB.NET and will confuse the upgrade wizard.

In previous versions of VB, if a Null value was passed to some functions, they were guaranteed to return Null without generating errors. (This is called "null propagation".) It's not supported in VB.NET.

Use Zero Bound Arrays. VB.NET Arrays always start at 0 (just like C/C++/Java


Use Visual Basic constants rather than hard-coded numbers in your code.

Get rid of fixed-length strings as they are no longer supported in VB.NET

Windows API calls are still supported, but be aware that the data types may change (Integer to Short, etc.) in their prototypes:


For preparation for the VB.NET Windows Forms classes (instead of VB 6 Forms) for client-side user interfaces, remember that:


The OLE, Shape, and Line controls are no longer supported.


Don't use Form methods like Circle, CLS, PSet, Line, and Point. .NET offers new calls to do graphics. (You will need to re-write this code yourself.)


You can no longer print windows forms with Form.PrintForm.


You can no longer disable a Timer control by setting its Interval to 0. Instead, set its Enabled property to False.


Taking all these into consideration, all the applications your business uses need to be assessed for a cost-benefit analysis before deciding to undertake the migration to .NET. Although Microsoft will stop supporting VB 6 in the future, that time is currently far down the road and might not come before an application outlives its usefulness. For most applications, I believe that the costs will be high, but the benefits will far outweigh these in the end.
__________________
Regards,
Muhammad Anis Ur Rehman

Miles to go Before I Sleep.

http://www.projekcarpet.com/anis.html
  #6  
Old 04-23-2002, 05:27 PM
10stone5
Guest
 
Posts: n/a
Default VB

I read not too long ago that VB code is either approaching or equal to Java in terms of amount of code in production. That is there are approximately an equal number of lines of VB code as Java code in production.

I wouldn't have thought about making this comparison a few years ago, when everyone told me to take up Java.
  #7  
Old 04-23-2002, 06:49 PM
Sid
Guest
 
Posts: n/a
Post

Apparently there will be a C# which will incorparate C++ and VB. Whether VB will continue, I don't know.
  #8  
Old 04-24-2002, 02:31 AM
divil's Avatar
divilWhat's the future hold for VB? divil is offline
Funky Monkey

* Expert *
 
Join Date: Nov 2001
Location: England
Posts: 1,289
Default

C# is a nice language. Whether you use C# or VB.NET will largely depend on what syntax you're most comfortable with. Personally I'm more comfortable with VB syntax, but I sometimes use C# because it's always good to learn another language.

VB has been miles ahead of Java for years. Java could have been good, but they blew it. Now it's only real use is on the server-side, and not even many people use it there.
__________________
MVP, C#
Now you see why evil will always triumph - because good is dumb.
Windows Forms and WPF user interface controls
  #9  
Old 04-24-2002, 08:34 AM
The IceMan
Guest
 
Posts: n/a
Default

well...

VB is so nice development tool, and used by many people...
i don't think they will just finish with that, maybe it can be remodulated, new procs and funcs but...

If VB is over...
I will lose my job !!

AAAAAAAAAHHHHHHHH

hauahauha
  #10  
Old 04-24-2002, 08:40 AM
orufet's Avatar
orufet orufet is offline
Paranoid Coder

Retired Leader
 
Join Date: Mar 2001
Location: Canada
Posts: 2,716
Default

Personal Computers will die in twenty-thrity years or so; when everything is automated enough, there won't be a need for a central computer system like a Gateway box, for example. Changes happen.
  #11  
Old 04-24-2002, 08:42 AM
Garrett Sever's Avatar
Garrett SeverWhat's the future hold for VB? Garrett Sever is offline
Strange Brewer

Retired Moderator
* Guru *
 
Join Date: Jun 2001
Location: AddressOf Insomnia
Posts: 2,815
Post

You will all be assimilated.

We will add your biological and technological knowledge to our own.

Resistance is futile.

http://run-fast.to/images/topics/microsoft.gif
__________________
"The lights below
You know they'll bleed forever
Get back as the cores blow
Let me fall..." - Dismantled, "Cornered"

Last edited by Garrett Sever; 04-24-2002 at 08:48 AM.
  #12  
Old 06-02-2002, 10:43 AM
Chazz569 Chazz569 is offline
Junior Contributor
 
Join Date: May 2002
Posts: 366
Default

Quote:
Originally posted by The Hand
You will all be assimilated.

We will add your biological and technological knowledge to our own.

Resistance is futile.

http://run-fast.to/images/topics/microsoft.gif
****! lol
  #13  
Old 06-02-2002, 12:14 PM
kannanvenkatesh's Avatar
kannanvenkatesh kannanvenkatesh is offline
Centurion
 
Join Date: May 2002
Location: INDIA
Posts: 99
Default

Iam relatively new to VB (novice). As far iam concerned VB is as famous as before. I have just dreamed about, making a useful software, one year back. But now iam making my dream come true by using VB. In the last six months or so, i've visited all kinds of VB sites and i still find hell lot of people buzzing around with all kinds of VB activities.

Iam sure VB will compete with other programming languages in forecoming years before .NET or higher version of VB taking its place.
__________________
Venki
  #14  
Old 06-02-2002, 12:49 PM
Banjo's Avatar
BanjoWhat's the future hold for VB? Banjo is offline
Hell's Angel

Retired Moderator
* Guru *
 
Join Date: Jul 2001
Location: Yorkshire, UK
Posts: 10,394
Default

It should be noted that there are some aspects of the .Net framework that can not used in VB.Net but can in C#. I can't remember the details but there are differences.
__________________
A wise one man once said "what you talking about dog breath"
  #15  
Old 06-02-2002, 01:58 PM
Techno Techno is offline
Senior Contributor
 
Join Date: Mar 2002
Location: Edinburgh
Posts: 983
Default

Regardless, I LOVE ALL PROGRAMMING LANGUAGES. I am wanting to learn all of them, although I only know a few.

I love ANY programming language or product Microsoft has made, never disrespected them.

If you treat things with respect, I am sure it will treat you back with respect (not that I am saying any of you DO treat them badly)

  #16  
Old 06-02-2002, 02:33 PM
Xilica2k2
Guest
 
Posts: n/a
Default

I agree Visual Basic is an easy language to learn but once you do it is very powerful. I do not think Visual Basic will go out of style for there are too many programmers for that. Then again, it would be helpful to get an early start, I think, on Visual Basic .NET since in the future everything will be .NET.
  #17  
Old 06-03-2002, 05:14 AM
divil's Avatar
divilWhat's the future hold for VB? divil is offline
Funky Monkey

* Expert *
 
Join Date: Nov 2001
Location: England
Posts: 1,289
Default

Quote:
Originally posted by Banjo
It should be noted that there are some aspects of the .Net framework that can not used in VB.Net but can in C#. I can't remember the details but there are differences.
And vice versa
__________________
MVP, C#
Now you see why evil will always triumph - because good is dumb.
Windows Forms and WPF user interface controls
  #18  
Old 06-03-2002, 03:15 PM
Banjo's Avatar
BanjoWhat's the future hold for VB? Banjo is offline
Hell's Angel

Retired Moderator
* Guru *
 
Join Date: Jul 2001
Location: Yorkshire, UK
Posts: 10,394
Post

Really? I didn't realise there was anything about .Net that could not be implemented in C#.
__________________
A wise one man once said "what you talking about dog breath"
  #19  
Old 06-04-2002, 12:20 PM
divil's Avatar
divilWhat's the future hold for VB? divil is offline
Funky Monkey

* Expert *
 
Join Date: Nov 2001
Location: England
Posts: 1,289
Default

Optional parameters spring to mind. C# can't do them.
__________________
MVP, C#
Now you see why evil will always triumph - because good is dumb.
Windows Forms and WPF user interface controls
Closed Thread


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
What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB? What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB? What's the future hold for VB?
What's the future hold for VB?
What's the future hold for VB?
 
What's the future hold for VB?
What's the future hold for VB?
 
-->