C.NET VS VB6

[AK]

Hello All,

We received this in response to a question we had posed at a trade show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have Database
access, would be web enabled so users set permissions, manipulate user
accounts, and billing over web, manipulate database information over the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development environment poses
its own risk to the development. In general, tools like Visual Basic are
most effective when
target features closely match their capabilities. When target features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend that
development be performed
in C#.NET. However, as long as you're willing to compromise your feature set
to match
the capabilities of Visual Basic, VB should deliver adequate results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your opinion
and a shortlist of those "feature sets" capabilities that VB does not do too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[Terry]

Just curious, why would the choice be between C#.Net vs. VB6 and not C#.Net
vs. VB.Net?
--
Terry
"AK" wrote:

Hello All,

We received this in response to a question we had posed at a trade show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have Database
access, would be web enabled so users set permissions, manipulate user
accounts, and billing over web, manipulate database information over the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development environment poses
its own risk to the development. In general, tools like Visual Basic are
most effective when
target features closely match their capabilities. When target features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend that
development be performed
in C#.NET. However, as long as you're willing to compromise your feature set
to match
the capabilities of Visual Basic, VB should deliver adequate results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your opinion
and a shortlist of those "feature sets" capabilities that VB does not do too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[Michel Posseth [MCP]]

if you were talking about VB.Net VS C#

In the features that you require both VB.Net and C# can do the job

i.m.h.o.

VB has some important extra`s for a project that C# not has

1. VB.Net programmers are easier to find
2. VB.net programmers are cheaper as C# programmers
3. VB is a true RAD platform
4. VB has a bigger and more active comunity

before a flamewar starts i also program in C# and find C# better for low
level stuff not because VB couldn`t do the job cause it can
but just for the fact that a lot of Java and C projects are ported to C# so
it is easier to find some docu on how to do stuff

regards

Michel Posseth [MCP]

"Terry" <Te***@nospam.nospamschreef in bericht
news:5E**********************************@microsof t.com...

Just curious, why would the choice be between C#.Net vs. VB6 and not
C#.Net
vs. VB.Net?
--
Terry
"AK" wrote:

>Hello All,

We received this in response to a question we had posed at a trade show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have Database
access, would be web enabled so users set permissions, manipulate user
accounts, and billing over web, manipulate database information over the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development environment
poses
its own risk to the development. In general, tools like Visual Basic are
most effective when
target features closely match their capabilities. When target features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend that
development be performed
in C#.NET. However, as long as you're willing to compromise your feature
set
to match
the capabilities of Visual Basic, VB should deliver adequate results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your
opinion
and a shortlist of those "feature sets" capabilities that VB does not do
too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[AK]

Hey Guys,

Thanks for the input..
In answer to the question about why I was asking about VB6 as opposed to
VB.net

We have a skunk worked concept prototype in VB6 simply because it was tool
that we had on the shelf when we stated kicking things around. It has done
well, but as you all know, these things can take on a life of their own as
far as scope creep to add features, and I am trying to look down the road.
If we take things further i just wanted to know how soon we were going to
run off a cliff with the various lanuguges. (Maybe we should port to
VB.net??? How is VB.net better that VB6??)

My assessment from prior shop-talk conversations with coders was that
various languages are better suited to various tasks. On pressing further,
though, I many times found that those that were dissing C++ for example
were not C++ shops, and those that were dissing VB or VB.net were C++ shops!
I alway have thought that such talk was kind of like saying "Fords are
crummy cars because I drive a Chevy"!
AK

"Terry" <Te***@nospam.nospamwrote in message
news:5E**********************************@microsof t.com...

Just curious, why would the choice be between C#.Net vs. VB6 and not
C#.Net
vs. VB.Net?
--
Terry
"AK" wrote:

>Hello All,

We received this in response to a question we had posed at a trade show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have Database
access, would be web enabled so users set permissions, manipulate user
accounts, and billing over web, manipulate database information over the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development environment
poses
its own risk to the development. In general, tools like Visual Basic are
most effective when
target features closely match their capabilities. When target features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend that
development be performed
in C#.NET. However, as long as you're willing to compromise your feature
set
to match
the capabilities of Visual Basic, VB should deliver adequate results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your
opinion
and a shortlist of those "feature sets" capabilities that VB does not do
too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[Michel Posseth [MCP]]

VB.Net vs VB6

VB.Net is a full featured OOP language , VB.Net is a .Net framework
development environment just as C# and J# C++.Net etc etc
so in the end they all run on the same .Net runtime ( so if one is faster
as the other it means they are coded differently ) as the different dev
environments all produce IL code that is feeded to the Runtime environment
..

>How is VB.net better that VB6

Well it is all a mather of preferences as a experienced VB6 and VB.Net
programmer i can tell you that in my opinion some parts of VB6 are superior
to VB.Net
however i also found the oposite true in many cases , as i make a living of
coding i choosed to go for the future and did not stick to VB6 ( although in
some occassions i still do some maintenance programming in VB6 ) ,,,, VB.Net
is the future for VB proggers

In the past in the C++, VB6 debate there were some bigger differences
C++ was more powerfull as VB6 however do you need a cruise missile to kill
a bug ?? VB6 was in a lot of situations the better choice as already in
this time VB6 was a RAD tool .

Now in the C# vs VB.Net erra we do not have these differences in power

So it is now a mather of personal coding preference ,,, do you feel
yourself at home in curly braced coding C++ , Java background or are you
a starting coder with a scientific background go for C# do you have a VB6
, Cobol , Fortran background or a starting coder who likes intuitive
language syntax go for VB.Net
regards

Michel Posseth [MCP]
"AK" <no****@satx.rr.comschreef in bericht
news:eR**************@TK2MSFTNGP04.phx.gbl...

Hey Guys,

Thanks for the input..
In answer to the question about why I was asking about VB6 as opposed to
VB.net

We have a skunk worked concept prototype in VB6 simply because it was tool
that we had on the shelf when we stated kicking things around. It has done
well, but as you all know, these things can take on a life of their own as
far as scope creep to add features, and I am trying to look down the road.
If we take things further i just wanted to know how soon we were going to
run off a cliff with the various lanuguges. (Maybe we should port to
VB.net??? How is VB.net better that VB6??)

My assessment from prior shop-talk conversations with coders was that
various languages are better suited to various tasks. On pressing further,
though, I many times found that those that were dissing C++ for example
were not C++ shops, and those that were dissing VB or VB.net were C++
shops! I alway have thought that such talk was kind of like saying "Fords
are crummy cars because I drive a Chevy"!
AK

"Terry" <Te***@nospam.nospamwrote in message
news:5E**********************************@microsof t.com...

>Just curious, why would the choice be between C#.Net vs. VB6 and not
C#.Net
vs. VB.Net?
--
Terry
"AK" wrote:

>>Hello All,

We received this in response to a question we had posed at a trade show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have Database
access, would be web enabled so users set permissions, manipulate user
accounts, and billing over web, manipulate database information over the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development environment
poses
its own risk to the development. In general, tools like Visual Basic are
most effective when
target features closely match their capabilities. When target features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend that
development be performed
in C#.NET. However, as long as you're willing to compromise your feature
set
to match
the capabilities of Visual Basic, VB should deliver adequate results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your
opinion
and a shortlist of those "feature sets" capabilities that VB does not do
too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[naraby]

hi,
AK i would recommend that you start reading an introductory chapter about
vb.net.
Personnally, I started writing in C and C++ when I was at the university.
Now I am using VB.net to write all my applications. Yet VB.NET 2005 is a
great addition to visual studio ....If you Microsoft Access then you will
find that it is easier to work with vb 2005.

"Michel Posseth [MCP]" wrote:

>
VB.Net vs VB6

VB.Net is a full featured OOP language , VB.Net is a .Net framework
development environment just as C# and J# C++.Net etc etc
so in the end they all run on the same .Net runtime ( so if one is faster
as the other it means they are coded differently ) as the different dev
environments all produce IL code that is feeded to the Runtime environment
..

How is VB.net better that VB6

Well it is all a mather of preferences as a experienced VB6 and VB.Net
programmer i can tell you that in my opinion some parts of VB6 are superior
to VB.Net
however i also found the oposite true in many cases , as i make a living of
coding i choosed to go for the future and did not stick to VB6 ( although in
some occassions i still do some maintenance programming in VB6 ) ,,,, VB.Net
is the future for VB proggers

In the past in the C++, VB6 debate there were some bigger differences
C++ was more powerfull as VB6 however do you need a cruise missile to kill
a bug ?? VB6 was in a lot of situations the better choice as already in
this time VB6 was a RAD tool .

Now in the C# vs VB.Net erra we do not have these differences in power

So it is now a mather of personal coding preference ,,, do you feel
yourself at home in curly braced coding C++ , Java background or are you
a starting coder with a scientific background go for C# do you have a VB6
, Cobol , Fortran background or a starting coder who likes intuitive
language syntax go for VB.Net
regards

Michel Posseth [MCP]
"AK" <no****@satx.rr.comschreef in bericht
news:eR**************@TK2MSFTNGP04.phx.gbl...

Hey Guys,

Thanks for the input..
In answer to the question about why I was asking about VB6 as opposed to
VB.net

We have a skunk worked concept prototype in VB6 simply because it was tool
that we had on the shelf when we stated kicking things around. It has done
well, but as you all know, these things can take on a life of their own as
far as scope creep to add features, and I am trying to look down the road.
If we take things further i just wanted to know how soon we were going to
run off a cliff with the various lanuguges. (Maybe we should port to
VB.net??? How is VB.net better that VB6??)

My assessment from prior shop-talk conversations with coders was that
various languages are better suited to various tasks. On pressing further,
though, I many times found that those that were dissing C++ for example
were not C++ shops, and those that were dissing VB or VB.net were C++
shops! I alway have thought that such talk was kind of like saying "Fords
are crummy cars because I drive a Chevy"!
AK

"Terry" <Te***@nospam.nospamwrote in message
news:5E**********************************@microsof t.com...

Just curious, why would the choice be between C#.Net vs. VB6 and not
C#.Net
vs. VB.Net?
--
Terry
"AK" wrote:

Hello All,

We received this in response to a question we had posed at a trade show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have Database
access, would be web enabled so users set permissions, manipulate user
accounts, and billing over web, manipulate database information over the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development environment
poses
its own risk to the development. In general, tools like Visual Basic are
most effective when
target features closely match their capabilities. When target features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend that
development be performed
in C#.NET. However, as long as you're willing to compromise your feature
set
to match
the capabilities of Visual Basic, VB should deliver adequate results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your
opinion
and a shortlist of those "feature sets" capabilities that VB does not do
too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[AK]

Thanks to you and Michael for the non-flamed information.
Uh Oh! Re: your mention of VB 2005 ... Is that something beyond VB.net, but
still of the VB lineage????... or is VB 2005 the predecessor. ??? or is VB
2005 something completely different?

I can tell that I have some studying up to do!

Thanks

AK

"naraby" <na****@discussions.microsoft.comwrote in message
news:E3**********************************@microsof t.com...

hi,
AK i would recommend that you start reading an introductory chapter about
vb.net.
Personnally, I started writing in C and C++ when I was at the university.
Now I am using VB.net to write all my applications. Yet VB.NET 2005 is a
great addition to visual studio ....If you Microsoft Access then you will
find that it is easier to work with vb 2005.

"Michel Posseth [MCP]" wrote:

>>
VB.Net vs VB6

VB.Net is a full featured OOP language , VB.Net is a .Net framework
development environment just as C# and J# C++.Net etc etc
so in the end they all run on the same .Net runtime ( so if one is
faster
as the other it means they are coded differently ) as the different dev
environments all produce IL code that is feeded to the Runtime
environment
..

>How is VB.net better that VB6

Well it is all a mather of preferences as a experienced VB6 and VB.Net
programmer i can tell you that in my opinion some parts of VB6 are
superior
to VB.Net
however i also found the oposite true in many cases , as i make a living
of
coding i choosed to go for the future and did not stick to VB6 ( although
in
some occassions i still do some maintenance programming in VB6 ) ,,,,
VB.Net
is the future for VB proggers

In the past in the C++, VB6 debate there were some bigger differences
C++ was more powerfull as VB6 however do you need a cruise missile to
kill
a bug ?? VB6 was in a lot of situations the better choice as already in
this time VB6 was a RAD tool .

Now in the C# vs VB.Net erra we do not have these differences in power

So it is now a mather of personal coding preference ,,, do you feel
yourself at home in curly braced coding C++ , Java background or are
you
a starting coder with a scientific background go for C# do you have a
VB6
, Cobol , Fortran background or a starting coder who likes intuitive
language syntax go for VB.Net
regards

Michel Posseth [MCP]
"AK" <no****@satx.rr.comschreef in bericht
news:eR**************@TK2MSFTNGP04.phx.gbl...

Hey Guys,

Thanks for the input..
In answer to the question about why I was asking about VB6 as opposed
to
VB.net

We have a skunk worked concept prototype in VB6 simply because it was
tool
that we had on the shelf when we stated kicking things around. It has
done
well, but as you all know, these things can take on a life of their own
as
far as scope creep to add features, and I am trying to look down the
road.
If we take things further i just wanted to know how soon we were going
to
run off a cliff with the various lanuguges. (Maybe we should port to
VB.net??? How is VB.net better that VB6??)

My assessment from prior shop-talk conversations with coders was that
various languages are better suited to various tasks. On pressing
further,
though, I many times found that those that were dissing C++ for
example
were not C++ shops, and those that were dissing VB or VB.net were C++
shops! I alway have thought that such talk was kind of like saying
"Fords
are crummy cars because I drive a Chevy"!
AK

"Terry" <Te***@nospam.nospamwrote in message
news:5E**********************************@microsof t.com...
Just curious, why would the choice be between C#.Net vs. VB6 and not
C#.Net
vs. VB.Net?
--
Terry
"AK" wrote:

Hello All,

We received this in response to a question we had posed at a trade
show
meeting. Our proposed app's target features consist of a business
application to crunch numbers, show forms, send emails and have
Database
access, would be web enabled so users set permissions, manipulate
user
accounts, and billing over web, manipulate database information over
the
web.

<Comment snip >

........."Also, the use of Visual Basic as the development
environment
poses
its own risk to the development. In general, tools like Visual Basic
are
most effective when
target features closely match their capabilities. When target
features
require the developer to
stretch the capabilities of the tool, it can result in significant,
unexpected development time. For
better flexibility in creating the application, we would recommend
that
development be performed
in C#.NET. However, as long as you're willing to compromise your
feature
set
to match
the capabilities of Visual Basic, VB should deliver adequate
results."

<End Comment snip>

Am I missing something? Could any of you give my the benefit or your
opinion
and a shortlist of those "feature sets" capabilities that VB does not
do
too
well at. I
thought the whole MS office suite had a VB backbone. What would be
compromised in VB6 as opposed to C#.net??
Thanks AK

[Lars G]

"AK" <no****@satx.rr.comskrev i en meddelelse
news:%2****************@TK2MSFTNGP03.phx.gbl...

Thanks to you and Michael for the non-flamed information.
Uh Oh! Re: your mention of VB 2005 ... Is that something beyond VB.net,
but still of the VB lineage????... or is VB 2005 the predecessor. ??? or
is VB 2005 something completely different?

I can tell that I have some studying up to do!

Why not download the free express version.

http://msdn.microsoft.com/vstudio/express/

or direct link to vb
http://msdn.microsoft.com/vstudio/express/vb/

[naraby]

VB 2005 IS THE LATEST VERSION of VB.NET
LARS GAVE YOU THE LINK TO DOWNLOAD THE FREE LIMITED CAPABILITY VERSION OF
VB.NET CALLED VB EXPRESS
http://msdn.microsoft.com/vstudio/express/vb/
I strongly recommend using it

"Lars G" wrote:

>
"AK" <no****@satx.rr.comskrev i en meddelelse
news:%2****************@TK2MSFTNGP03.phx.gbl...

Thanks to you and Michael for the non-flamed information.
Uh Oh! Re: your mention of VB 2005 ... Is that something beyond VB.net,
but still of the VB lineage????... or is VB 2005 the predecessor. ??? or
is VB 2005 something completely different?

I can tell that I have some studying up to do!

Why not download the free express version.

http://msdn.microsoft.com/vstudio/express/

or direct link to vb
http://msdn.microsoft.com/vstudio/express/vb/

[Steven Nagy]

Naraby, here's a great resource for you:
http://www.google.com.au/search?hl=e...e+Search&meta=

Good luck putting it into practise!
naraby wrote:

VB 2005 IS THE LATEST VERSION of VB.NET
LARS GAVE YOU THE LINK TO DOWNLOAD THE FREE LIMITED CAPABILITY VERSION OF
VB.NET CALLED VB EXPRESS
http://msdn.microsoft.com/vstudio/express/vb/
I strongly recommend using it

[Michael D. Ober]

Clarification:

The express editions are the same compilers found in VS 2005 versions. The
only limits are in the development IDEs.

Mike Ober.

"naraby" <na****@discussions.microsoft.comwrote in message
news:FE**********************************@microsof t.com...

VB 2005 IS THE LATEST VERSION of VB.NET
LARS GAVE YOU THE LINK TO DOWNLOAD THE FREE LIMITED CAPABILITY VERSION OF
VB.NET CALLED VB EXPRESS
http://msdn.microsoft.com/vstudio/express/vb/
I strongly recommend using it

"Lars G" wrote:

>>
"AK" <no****@satx.rr.comskrev i en meddelelse
news:%2****************@TK2MSFTNGP03.phx.gbl...

Thanks to you and Michael for the non-flamed information.
Uh Oh! Re: your mention of VB 2005 ... Is that something beyond
VB.net,
but still of the VB lineage????... or is VB 2005 the predecessor. ???
or
is VB 2005 something completely different?

I can tell that I have some studying up to do!

Why not download the free express version.

http://msdn.microsoft.com/vstudio/express/

or direct link to vb
http://msdn.microsoft.com/vstudio/express/vb/