Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / General 2 / February 2005



Tip: Looking for answers? Try searching our database.

VB vs VB.NET

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
TC - 25 Feb 2005 19:16 GMT
Are there any compelling reasons to use one over the other?
Dag Sunde - 25 Feb 2005 19:35 GMT
> Are there any compelling reasons to use one over the other?

Apples & Oranges...

Besides one packs a 20Mb runtime that needs
to be redistributed/present...
Matthew Hanna - 25 Feb 2005 19:57 GMT
> Are there any compelling reasons to use one over the other?

.NET because Microsoft said so.  I am the rebellious type though.
David Segall - 26 Feb 2005 13:01 GMT
>Are there any compelling reasons to use one over the other?
Microsoft think there are.
<(http://msdn.microsoft.com/vbasic/support/vb6.aspx)>
Bob Butler - 26 Feb 2005 15:19 GMT
> Are there any compelling reasons to use one over the other?

IMO the possible reason not to use VB is that MS is dropping it and
long-term support and maintenance for applications is likely to become
more and more problematical.

OTOH I have yet to find *any* reason to consider VB.Net a good choice
given that MS has so clearly made it obvious that they have no regard
for VB as anything other than a toy language that can be trashed at
will.  If you decide to go .Net you should seriously consider using C#
as that looks to have a better chance at survival and stability.
Steve Gerrard - 26 Feb 2005 16:34 GMT
| > Are there any compelling reasons to use one over the other?
|
[quoted text clipped - 7 lines]
| will.  If you decide to go .Net you should seriously consider using C#
| as that looks to have a better chance at survival and stability.

As far as support for VB6, despite the link David Segal posted claiming
2008 is the cut off, MS has effectively dropped support for VB already.
No more service packs or fixes, no help with bugs and issues. The
support for VB6 has been groups like this one for a while now.

Instead of VB.Net, they should have called it VB#. It has the same
relationship to VB that C# has to C++, that is, the same general syntax,
but a totally different code model. Plus they use the same CLR and more
or less the same compiler.

The real question is do you want an ActiveX/COM type of programming
tool, or a .Net Framework type of tool. If you run AutoCAD LT 2000 and
AutoCAD LT 2005 side by side, you can see what happens with a .Net
program - much slower start up time, no improvement in user interface,
the addition of networking and Internet doo-dads for updating widget
libraries and publishing files.
Frank Adam - 26 Feb 2005 17:20 GMT
>Are there any compelling reasons to use one over the other?

Yawn, is it that time of the year again ?
Wake me up in a week or two..

Signature

Regards, Frank

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.