6.0 or .NET?

[Ilkka]

Hi,

I'm trying to select the language for next Windows application and have
approx two choices: VB 6.0 and VB.NET.

I wouldn't want to require the .NET framework be installed along the
product: can I make old style VB applications with VB.NET? Does VB.NET
applications always require the .NET framework?

Any other thoughts how to make the selection? I guess 6.0 apps can always be
converted to .NET later?

Thanks,
Ilkka

 

[Jan Tielens]

If you don't want to install the .NET Framework on your client pc's, then
you MUST use VB6. In VB.NET you can only develop for the .NET Framework.

There is an upgrade wizard for VB6 to VB.NET, but be aware that this won't
work for 100%.

--
Greetz

Jan Tielens
________________________________
Read my weblog: http://weblogs.asp.net/jan

 

[Cor]

Hi Ikka,

As addition to Jan

In .Net is the runtimer integratted.
in VB6 you need always to install the runtimer, the only difference is, that
you are used to install it with your package and in VB.net it is a seperate
install..

When you are converting VB6 to VB.net it is not totaly converted, an very
big deal is done in a VisualBasic6 compatible part. (Dont mix this up with
the Microsoft.VisualBasic that is something else)

I hope this helps,

Cor

 

[Ilkka]

Thanks!

Ok, 6.0 it is then, this cleared it out. .NET can wait until the framework
doesn't need to be installed separately...(sometime in the distant future).

If someone wants to sell me Visual Studio 6.0 Pro Full license +CDs (not
manuals needed) and ship it to Finland (I'll pay the expenses), send me
email.

Ilkka

 

[Blumidoo]

I wouldn't want to require the .NET framework be installed along the

product: can I make old style VB applications with VB.NET? Does VB.NET
applications always require the .NET framework?

If that is your main concern, you should stick to 6.0. However, please
reconsider your choice, because VB.NET is way more powerful than VB 6.0. You
will design, implement and maintain your application faster and easier with
..NET

Any other thoughts how to make the selection? I guess 6.0 apps can always be
converted to .NET later?

Converted - yes, but at what cost...? You will end up with an unmaintainable
code that does not benefit from .NET features. If I were to choose, I'd
choose .NET and bundle .NET Framework instalation into the setup.
..NET Framework is not that evil to install anyway... it is like with games -
you'll need the latest DirectX to run most of them.

Go for .NET!

sincerely,
--
Sebastian Zaklada
Skilled Software
http://www.skilledsoftware.com
************************************
SQL Source Control 2003 - for
SQL Server Source Safe integration
and custom databases documentation

 

[Ilkka]

If that is your main concern, you should stick to 6.0. However, please

reconsider your choice, because VB.NET is way more powerful than VB 6.0. You
will design, implement and maintain your application faster and easier with
.NET
code that does not benefit from .NET features.

I'm not sure if I need .NET features. I will need Longhorn features, that I
know, but .NET I'm not sure of. And Longhorn is still a bit ahead from now.

I'm not afraid to convert the app manually to VB.NET; I already need to
convert the app from PHP to VB in the first place So at least I will get
intimately familiar with the code, and there cannot be such drastic
differences between VB6.0 and VB.NET ... I suppose...

Another point to consider would be if VB is fast enough, compared to C, but
I guess/hope so Of course it depends what you are doing...well..it's
"basic stuff".

Ilkka

 

[Brian Henry]

just remember, .NET can do so much more then VB6.0 can do and has lots of
features preprogrammed for you to use. the class libary is very big. and,
like .NET you still have to have VB runtimes installed on all client
machiens you will run VB6 on also, either version you still must have the
runtimes installed

 

[Brian Henry]

if your going frmo PHP to VB, go with VB.NET because it's object oriented,
similar to PHP, while VB you would have a lot of trouble converting
everything over to with out some very interesting work arounds

 

[Herfried K. Wagner [MVP]]

I'm trying to select the language for next Windows application and have
approx two choices: VB 6.0 and VB.NET.

I wouldn't want to require the .NET framework be installed along the
product: can I make old style VB applications with VB.NET? Does VB.NET
applications always require the .NET framework?

You will have to use VB6, but notice that even VB6 requires its
runtimes.

Any other thoughts how to make the selection? I guess 6.0 apps can always be
converted to .NET later?

They can, but it's often easier/better to rewrite the whole application
in .NET.

 

[Jay B. Harlow [MVP - Outlook]]

Ilkka,
In addition to the others comments.

I'm not sure if I need .NET features. I will need Longhorn features, that I
know, but .NET I'm not sure of. And Longhorn is still a bit ahead from

now.
If you know you will need Longhorn features, I hope you know they will
mostly be exposed via managed types! VB.NET does managed types, VB6 does
not.

If you use VB6 now, you will have even more to learn when you go to
Longhorn, however if you go VB.NET now you will have already learned about
using .NET, making the stop to Longhorn easier!

Also VB6 & VB.NET are different beasts, you will need to learn VB6, then you
will need to relearn VB.NET, hopefully dropping the "bad habits" picked up
in VB6.

Coming from PHP & ultimately going to Longhorn, it would seem to me that it
would be better to go to VB.NET now. Remember PHP & VB.NET are both OOP,
while VB6 is Object Based development.

Yes every one who uses your app will need to have the Framework installed,
however I understand that more and more machines are shipping with the
Framework pre-installed. The Framework only needs to be installed once, then
all .NET applications can use it. For the most part only version 1.0 or 1.1
of the framework needs to be installed. Given the option I would recommend
1.1, unless the user has an app that absolutely requires 1.0.

Hope this helps
Jay

 

[One Handed Man [ OHM# ]]

I heard that they are delivering a sister product to Longhorn in the fall of
2008,its called LongWait.

OHM

Ilkka,
In addition to the others comments.
now.
If you know you will need Longhorn features, I hope you know they will
mostly be exposed via managed types! VB.NET does managed types, VB6
does not.

If you use VB6 now, you will have even more to learn when you go to
Longhorn, however if you go VB.NET now you will have already learned
about using .NET, making the stop to Longhorn easier!

Also VB6 & VB.NET are different beasts, you will need to learn VB6,
then you will need to relearn VB.NET, hopefully dropping the "bad
habits" picked up in VB6.

Coming from PHP & ultimately going to Longhorn, it would seem to me
that it would be better to go to VB.NET now. Remember PHP & VB.NET
are both OOP, while VB6 is Object Based development.

Yes every one who uses your app will need to have the Framework
installed, however I understand that more and more machines are
shipping with the Framework pre-installed. The Framework only needs
to be installed once, then all .NET applications can use it. For the
most part only version 1.0 or 1.1 of the framework needs to be
installed. Given the option I would recommend
1.1, unless the user has an app that absolutely requires 1.0.

Hope this helps
Jay

Regards - OHM# OneHandedMan{at}BTInternet{dot}com

 

[Aphrodite]

-----Original Message-----
Hi,

I'm trying to select the language for next Windows application and have
approx two choices: VB 6.0 and VB.NET.

Hi, unfortunately you need the Framework to write in
VB.NET .

Well if you are happy with VB6 don't change it yet to .NET

..NET in terms of thinking is different since it is totally
object-oriented(like Java or C++).

Good Luck,

Aphro

 

[CJ Taylor]

I'm sorry, but I cannot believe that no one has commented on this yet.

Is this a joke?

You have to understand why I ask this. Because it is quite obvious you know
nothing of what you are talking about. I don't mean to be a d**k or
anything like that, I'm just seeing some grotesqely misstated things. I'm
going to answer your questions below as well, or at least retort in some way
to this. And my hope is that you get a true understanding of what your even
trying to accomplish. Or, if your just yanking our chain.

I'm not sure if I need .NET features. I will need Longhorn features, that I
know, but .NET I'm not sure of. And Longhorn is still a bit ahead from now.

If you have read even the basic information about Longhorn, you will notice
that .NET is a key part of the longhorn project. The goal is to let the
..NET framework provide more low level functions like its predecessor and
soon to be sibling the Win32API. What used to be .NET's seemingly only
drawback to not be able to provide that instense lowlevel functionality
within managed code is now ending.

So if you need longhorn... you need .NET. Otherwise, you have no idea what
longhorn is capable of. Hell, Win2k3 even made development easier. Now
they have feedback from developers like those of us in this forum and can
develop an even more powerful product.

I'm not trying to rag on you, but if you think you know what longhorn offers
without seeing the OBVIOUS signs of .NET, then you need to keep reading.

I'm not afraid to convert the app manually to VB.NET; I already need to
convert the app from PHP to VB in the first place So at least I will get
intimately familiar with the code, and there cannot be such drastic
differences between VB6.0 and VB.NET ... I suppose...

See... this doesn't make sense. As someone else stated PHP is more of an
OOP than VB6. So its quite clear that A) you would want to go to another OO
language like .NET, or b) the php code sucked giving you bad habits.

Thats the thing. VB6 develops a LOT of really really really bad habits that
are hard to break. Just avoid it if you can.

Another point to consider would be if VB is fast enough, compared to C, but
I guess/hope so Of course it depends what you are doing...well..it's
"basic stuff".

Basic stuff? And speed? Yeah, C is "faster", but takes you a lot longer to
develop in. And your doing a conversion project. I dunno dude, kinda
sounds like cutting your rim in half to change your tire...

 

[Ilkka]

Is this a joke?

No. Maybe just some different kind of reasoning to catch some attention

If you have read even the basic information about Longhorn, you will notice
that .NET is a key part of the longhorn project.
So if you need longhorn... you need .NET.

Yes, I was assuming (ie. had the idea) that .NET is part of Longhorn, but
that's not the point. The point is that I don't need .NET alone to do what I
want to do. Only Longhorn brings some changes that I will need to adjust
to/take advantage of, but .NET doesn't bring those requirements to me.
Longhorn changes some things that are different in current systems (XP +
..NET for example).

See... this doesn't make sense. As someone else stated PHP is more of an
OOP than VB6. So its quite clear that A) you would want to go to another OO
language like .NET, or b) the php code sucked giving you bad habits.

Yes, I see some advantage in VB.NET being OOP. However, this particular app
of mine, it's not totally OOP, it's a mix of functional approach and object
oriented approach, and I'm pretty sure I can work things out with no classes
at all - I just modularize them somehow to resemble classes in some way. The
classes are there to keep me informed of the code's structure, which works
fine, but they are not really required by any functional or other means.
Just a nice way to group code.

Thats the thing. VB6 develops a LOT of really really really bad habits that
are hard to break. Just avoid it if you can.

We'll see about that Of course I would choose .NET but I'm really
concerned about this framework installing part - unless Microsoft will put
..NET framework in Window XP SP2, for example, or would have put it in XP /XP
+ SP1 in the first place (or did they?).

Basic stuff? And speed? Yeah, C is "faster", but takes you a lot longer to
develop in.

Yes, I hate the strings in C, be it a bit more sensible there, C would be
good This app is a lot about strings. Ok, maybe there are some nice
libraries with regexps that I should consider.

And your doing a conversion project. I dunno dude, kinda
sounds like cutting your rim in half to change your tire...

Thanks for the feedback to all, everybody has given good points to consider


Ilkka