okay, so i'm gonna buy VB6.0...which one? professional or enterprise??

[spewn]

can someone tell me the difference besides $$ between Visual Basic, 6.0 Professional and/or Enterprise editions??

perhaps more in depth that just your preference...like limitations, scope, strengths, etc...

can you create the same (visually) with both? what features are diff?

any help is appreciated, (the more in depth, the better...)


- spewn

 

[jsnull]

The enterprise edition is ideal for when you have multiple developers working on a project ... i.e., enterprise. If you're working on your own projects on your own PC, and not sharing project develop, VB6.0 Professional is perfect.

Jim
Web:

http://www.jimnull.com

Email: jim@jimnull.com

 

[CajunCenturion]

If you're just getting started, then perhaps .Net may be the way to go since VB6 is on the way out the door.
Good Luck
------------
Select * from Users where Clue > 0
0 rows returned

 

[chadt]

VB 6 is still going to be a major player so its really not just out the door. M$ already has plans to support VB6 for years to come....however VB.NET is alot cleaner but if your going to learn VB.NET you might as well do the right thing and learn C# instead.

 

[spewn]

what is .net? i've seen it around...you can create applications just like VB?

what are its strengths, weaknesses?

why do you say it's on the way out the door?

as far as the enterprise vs. professional, you don't get any special features other than multiple developers?


- spewn

 

[Swi]

.Net is the newest version of VB. Supposedly Microsoft has already stopped selling VB 6. I only forsee Microsoft supporting VB 6 for about another year and a half. I would go with .Net if I were you. I will soon be upgrading myself after I do some more research.

 

[Guest_imported]

VB5 & 6 are certainly "outdated" products... However, as long as Windows
continues to support the Win32 API, you'll be able to write 32 bit VB apps
for it. Certainly there will be some features that you cannot develop (COM+,
Web Services already).

Microsoft is committed to .Net. It is the framework of the future, and it is
probable that some future version of Windows will drop the Win32 API and
work only with .Net. However, I would estimate that to be very far in the
future - 10 years or more.

I don't think .Net is ready for the general application programmer. It isn't
reasonable to force users to install the 17+ meg .Net framework just to run
your application. There are certainly many advantages to .Net, but many of
them only apply in a large, scalable-necessary network environment and don't
really apply to your average desktop application programmer.

If you are thinking about converting legacy applications - don't, unless you
have a strong need for .Net-specific features. .Net programming is
fundamentally different than Win32 programming. VB.Net adds OOP capability,
and the only reason I would switch, other than a need for specific .Net
features, would be for the added structure and ease of maintenance and all
that other junk you get with OOP apps. Even then, I would only convert an
app that was relatively small right now but would be getting very large with
lots of people working on it.

Also note that Win32 is still *directly* supported by .Net - VC++ 7 refers
to VC.Net in "unmanaged code" mode. Pretty much that means VC++ 6 with a few
fixes - mostly improved ANSI C++ support. Only caveat is, of course, you
gotta program in C++ and not VB.

 

[chadt]

M$ has not stopped selling VB6....I can't even beleive that was posted here....VB6 is still around and you can still buy it....and for the part about support for only a year and a half....thats another thing I can't believe has been posted.........It will take that long for many companies to port their code to .NET. We have over 1 Million lines of VB code here and there is no way it would all be ported over in a year and a half . The last post I saw support for more like ten years seems more realistic. .NET has many advantages over VB6....just for starters...the IDE rocks....I love the expandable code regions.

 

[strongm]

I can't believe it was posted either.

Even VB4, whilst grantedly no longer available, is still supported by Microsoft.

 

[CajunCenturion]

You may very well be correct Chadt, but I invite you to the following page:

http://msdn.microsoft.com/library/d...y/devprods/vs6/vbasic/vbcon98/vbstartpage.htm

See what is in red at the top of the page. I suggest that may be the "handwriting on the wall"

Good Luck
------------
Select * from Users where Clue > 0
0 rows returned

 

[chadt]

That just states that the MSDN documentation is not being updated anymore. No big deal as it wasn't updated that much in the past year anyways.