Re: C.NET VS VB6

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


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" <nospam@xxxxxxxxxxx> schreef in bericht
news:eR0gCkDqGHA.4812@xxxxxxxxxxxxxxxxxxxxxxx
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" <Terry@xxxxxxxxxxxxx> wrote in message
news:5E8C4116-79B6-426A-B4DB-4662CF12FD7F@xxxxxxxxxxxxxxxx
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







.

Relevant Pages

  • Re: VB6 vs VB .Net
    ... I still think the best programs are the assembly language programs. ... All differences are explained to you and porting VB6 to VB.NET will not be ... > partially due to the IDE, but also due to the improved language features. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 vs VB .Net
    ... If you decide to stick with VB6 for a while longer, ... even more so than any other .NET language. ... but also due to the improved language features. ... On the client side of things, especially as it sounds like you will be doing ...
    (microsoft.public.vb.general.discussion)
  • Re: Newbie Advice/Critiscism
    ... the Office Development Team and the Language group. ... There were papers and some 'demos' showing these features. ... started phasing out VB when VB6 was released. ... didn't mind that much, as it was after all, Beta 0.9. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 vs VB .Net
    ... All differences are explained to you and porting VB6 to VB.NET will not be ... > even more so than any other .NET language. ... > partially due to the IDE, but also due to the improved language features. ... > your client requirements. ...
    (microsoft.public.vb.general.discussion)
  • Re: Newbie Advice/Critiscism
    ... If I remember correctly from a couple/few years ago, Karl once posted a ... the Office Development Team and the Language group. ... There were papers and some 'demos' showing these features. ... started phasing out VB when VB6 was released. ...
    (microsoft.public.vb.general.discussion)