Choosing a programming language for use in the future...

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • murl

    Choosing a programming language for use in the future...

    I currently am programming apps using the vb.net language and haven't
    seen to many problems with it, since migrating from vb6. I love the
    enviornment, and the ease of use but wonder could my apps be better in
    c#? I have studied vb6, vb.net, and c++, and am currently learning
    alot about c#, and will be doing quite a few more applications in the
    future. Technically i could learn any programming language and stick
    with it, but is that one the right one is the question. I will be
    buidling quite a lot of custom controls, windows applications, and web
    development projects and was wanting to know if anyone else has any
    insight on why i should stick with vb.net, and not move to c# and
    dedicate all future development in that language. In my mind c# looks
    as if it complies to less code, and the apps use less memory, but on
    the other hand vb.net code is easier to look at on the eyes, and
    navigate around. I know there are many other differences in statemnt
    blocks, variable declaration and other dark aspects of it, but im not
    aware of them. Any insight on this subject would be great.

    Thanks,
    Murl
  • Chad Z. Hower aka Kudzu

    #2
    Re: Choosing a programming language for use in the future...

    murl@cbsmemphis .com (murl) wrote in news:a11c4534.0 401261406.4a527 555
    @posting.google .com:[color=blue]
    > enviornment, and the ease of use but wonder could my apps be better in
    > c#? I have studied vb6, vb.net, and c++, and am currently learning[/color]

    No. With .net everything is the same. Language is now just a personal
    preference.



    --
    Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
    "Programmin g is an art form that fights back"


    ELKNews - Get your free copy at http://www.atozedsoftware.com

    Comment

    • Nicholas Paldino [.NET/C# MVP]

      #3
      Re: Choosing a programming language for use in the future...

      Murl,

      If you are comfortable with VB.NET and find yourself most productive
      with it, then I couldn't say that you should go to C#, only because the
      benefits that you are going to gain are not much, considering that
      everything compiles down to IL code. While the code that IL code that C#
      spits out and VB spits out is not the same, it is close enough that you
      don't see perf issues (for the most part).

      Also, with the return of edit and continue in the next version of
      VS.NET, I imagine that a lot of VB'ers will be very, very happy.

      Hope this helps.


      --
      - Nicholas Paldino [.NET/C# MVP]
      - mvp@spam.guard. caspershouse.co m

      "murl" <murl@cbsmemphi s.com> wrote in message
      news:a11c4534.0 401261406.4a527 555@posting.goo gle.com...[color=blue]
      > I currently am programming apps using the vb.net language and haven't
      > seen to many problems with it, since migrating from vb6. I love the
      > enviornment, and the ease of use but wonder could my apps be better in
      > c#? I have studied vb6, vb.net, and c++, and am currently learning
      > alot about c#, and will be doing quite a few more applications in the
      > future. Technically i could learn any programming language and stick
      > with it, but is that one the right one is the question. I will be
      > buidling quite a lot of custom controls, windows applications, and web
      > development projects and was wanting to know if anyone else has any
      > insight on why i should stick with vb.net, and not move to c# and
      > dedicate all future development in that language. In my mind c# looks
      > as if it complies to less code, and the apps use less memory, but on
      > the other hand vb.net code is easier to look at on the eyes, and
      > navigate around. I know there are many other differences in statemnt
      > blocks, variable declaration and other dark aspects of it, but im not
      > aware of them. Any insight on this subject would be great.
      >
      > Thanks,
      > Murl[/color]


      Comment

      • Jose Caliente

        #4
        Re: Choosing a programming language for use in the future...

        lear C# !

        jc



        "Chad Z. Hower aka Kudzu" <cpub@hower.org > wrote in message
        news:Xns947DD33 E852Bcpub@127.0 .0.1...[color=blue]
        > murl@cbsmemphis .com (murl) wrote in news:a11c4534.0 401261406.4a527 555
        > @posting.google .com:[color=green]
        > > enviornment, and the ease of use but wonder could my apps be better in
        > > c#? I have studied vb6, vb.net, and c++, and am currently learning[/color]
        >
        > No. With .net everything is the same. Language is now just a personal
        > preference.
        >
        >
        >
        > --
        > Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
        > "Programmin g is an art form that fights back"
        >
        >
        > ELKNews - Get your free copy at http://www.atozedsoftware.com
        >[/color]


        Comment

        • phoenix

          #5
          Re: Choosing a programming language for use in the future...

          Not really. There's one thing why I prefer C#, though I hardly ever use it :
          unsafe code.

          Try manipulating the bits of a bitmap in VB.Net and you will notice what I
          mean. But unless you're interested in graphic stuff like that (and maybe
          some advanced math routines), unsafe code doesn't really have that much use.

          Yves

          "Chad Z. Hower aka Kudzu" <cpub@hower.org > schreef in bericht
          news:Xns947DD33 E852Bcpub@127.0 .0.1...[color=blue]
          > murl@cbsmemphis .com (murl) wrote in news:a11c4534.0 401261406.4a527 555
          > @posting.google .com:[color=green]
          > > enviornment, and the ease of use but wonder could my apps be better in
          > > c#? I have studied vb6, vb.net, and c++, and am currently learning[/color]
          >
          > No. With .net everything is the same. Language is now just a personal
          > preference.
          >
          >
          >
          > --
          > Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
          > "Programmin g is an art form that fights back"
          >[/color]


          Comment

          • Hector Martinez

            #6
            Re: Choosing a programming language for use in the future...



            Excuse me, but I had never wrote code in VB, what you mean with "...edit and continue..."?



            Thanx in advantage.

            Comment

            • Scott M.

              #7
              Re: Choosing a programming language for use in the future...

              Isn't Edit & Continue already in VS.NET 2002?

              Tools...Options ...Debugging... .Edit & Continue...Allo w Me To Edit VB Files
              While Debugging


              [color=blue]
              > Also, with the return of edit and continue in the next version of
              > VS.NET, I imagine that a lot of VB'ers will be very, very happy.[/color]


              Comment

              • Nicholas Paldino [.NET/C# MVP]

                #8
                Re: Choosing a programming language for use in the future...

                Hector,

                Edit and Continue was a feature in VB6 (and previous versions, although
                I forget which ones) which allowed you to stop code execution at some point,
                edit code, and then continue from that point on without stopping the program
                and recompiling.


                --
                - Nicholas Paldino [.NET/C# MVP]
                - mvp@spam.guard. caspershouse.co m

                "Hector Martinez" <anonymous@disc ussions.microso ft.com> wrote in message
                news:FA2D6E6D-D0B1-4AC7-A572-79BB4C957972@mi crosoft.com...[color=blue]
                >
                >
                > Excuse me, but I had never wrote code in VB, what you mean with[/color]
                "...edit and continue..."?[color=blue]
                >
                >
                >
                > Thanx in advantage.[/color]


                Comment

                • Jay B. Harlow [MVP - Outlook]

                  #9
                  Re: Choosing a programming language for use in the future...

                  Scott,
                  That does not cause the line you change to be dynamically recompiled...
                  VS.NET 2002 & VS.NET 2003 will force to stop, compile & then rerun your
                  program.

                  Edit & Continue is the VB6 feature that when you stop at a break point you
                  can modify the source, and the modification is immediately reflected in any
                  statements that you then execute.

                  Hope this helps
                  Jay

                  "Scott M." <s-mar@BADSPAMsnet .net> wrote in message
                  news:%23jOyr7F5 DHA.504@TK2MSFT NGP11.phx.gbl.. .[color=blue]
                  > Isn't Edit & Continue already in VS.NET 2002?
                  >
                  > Tools...Options ...Debugging... .Edit & Continue...Allo w Me To Edit VB Files
                  > While Debugging
                  >
                  >
                  >[color=green]
                  > > Also, with the return of edit and continue in the next version of
                  > > VS.NET, I imagine that a lot of VB'ers will be very, very happy.[/color]
                  >
                  >[/color]


                  Comment

                  • Bram

                    #10
                    Re: Choosing a programming language for use in the future...

                    Hi,

                    I should use whatever feels most comfortable to me to get the job done.
                    That's why your boss (or at least most of them) is paying you in the first
                    place, to get the job done in time.
                    Unless you are your own, of course. But then again, you still might have
                    some deadlines to meet.
                    Don't hesitate to learn C# if you've got the time. IMO the cleanest .NET
                    language (oops, might be my C/C++ background here).
                    It was build from scratch to take full advantage of .NET (while looking at
                    other languages C++, Java, Delphi, ... leaving the bad things out and the
                    good ones in).
                    As mentioned by others, assemblies produces by VB.NET will be virtually the
                    same as those produces by other .NET languages, unless you are doing some
                    low level language-specific stuff. I suggest putting as much code as
                    possible within libraries. This way you can always reuse it in the other
                    ..NET languages.

                    Greetings,

                    Bram.



                    "murl" <murl@cbsmemphi s.com> wrote in message
                    news:a11c4534.0 401261406.4a527 555@posting.goo gle.com...[color=blue]
                    > I currently am programming apps using the vb.net language and haven't
                    > seen to many problems with it, since migrating from vb6. I love the
                    > enviornment, and the ease of use but wonder could my apps be better in
                    > c#? I have studied vb6, vb.net, and c++, and am currently learning
                    > alot about c#, and will be doing quite a few more applications in the
                    > future. Technically i could learn any programming language and stick
                    > with it, but is that one the right one is the question. I will be
                    > buidling quite a lot of custom controls, windows applications, and web
                    > development projects and was wanting to know if anyone else has any
                    > insight on why i should stick with vb.net, and not move to c# and
                    > dedicate all future development in that language. In my mind c# looks
                    > as if it complies to less code, and the apps use less memory, but on
                    > the other hand vb.net code is easier to look at on the eyes, and
                    > navigate around. I know there are many other differences in statemnt
                    > blocks, variable declaration and other dark aspects of it, but im not
                    > aware of them. Any insight on this subject would be great.
                    >
                    > Thanks,
                    > Murl[/color]


                    Comment

                    • Scott M.

                      #11
                      Re: Choosing a programming language for use in the future...

                      Ok, thanks Jay.


                      "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_MVP @msn.com> wrote in message
                      news:%23$Xi7cG5 DHA.360@TK2MSFT NGP12.phx.gbl.. .[color=blue]
                      > Scott,
                      > That does not cause the line you change to be dynamically recompiled...
                      > VS.NET 2002 & VS.NET 2003 will force to stop, compile & then rerun your
                      > program.
                      >
                      > Edit & Continue is the VB6 feature that when you stop at a break point you
                      > can modify the source, and the modification is immediately reflected in[/color]
                      any[color=blue]
                      > statements that you then execute.
                      >
                      > Hope this helps
                      > Jay
                      >
                      > "Scott M." <s-mar@BADSPAMsnet .net> wrote in message
                      > news:%23jOyr7F5 DHA.504@TK2MSFT NGP11.phx.gbl.. .[color=green]
                      > > Isn't Edit & Continue already in VS.NET 2002?
                      > >
                      > > Tools...Options ...Debugging... .Edit & Continue...Allo w Me To Edit VB[/color][/color]
                      Files[color=blue][color=green]
                      > > While Debugging
                      > >
                      > >
                      > >[color=darkred]
                      > > > Also, with the return of edit and continue in the next version of
                      > > > VS.NET, I imagine that a lot of VB'ers will be very, very happy.[/color]
                      > >
                      > >[/color]
                      >
                      >[/color]


                      Comment

                      • Jon Skeet [C# MVP]

                        #12
                        Re: Choosing a programming language for use in the future...

                        piddie <avateaforme@di ne83kdk.net> wrote:[color=blue]
                        > "... so it shouldn't matter, in theory, which one you choose. However,
                        > the theory doesn't work in practice. All .Net languages do compile to
                        > IL, but not to the same IL. The performance and efficiency of the IL
                        > each language generates depends on how well that language's compiler
                        > optimizes the output." --- Visual Studio Magazine.
                        >
                        > Apparently this is expected to become more pronounced in the future.[/color]

                        Who expects it to become more pronounced? I'd expect it to become
                        *less* pronounced, personally.

                        --
                        Jon Skeet - <skeet@pobox.co m>
                        Pobox has been discontinued as a separate service, and all existing customers moved to the Fastmail platform.

                        If replying to the group, please do not mail me too

                        Comment

                        • Scott M.

                          #13
                          Re: Choosing a programming language for use in the future...

                          From what source do you get this:

                          [color=blue]
                          > "... so it shouldn't matter, in theory, which one you choose. However,
                          > the theory doesn't work in practice. All .Net languages do compile to
                          > IL, but not to the same IL. The performance and efficiency of the IL
                          > each language generates depends on how well that language's compiler
                          > optimizes the output." --- Visual Studio Magazine.
                          >
                          > Apparently this is expected to become more pronounced in the future.
                          >
                          >
                          >[/color]


                          Comment

                          • Abubakar

                            #14
                            Re: Choosing a programming language for use in the future...

                            Recently some spisode of .NET ROCKS! show discussed how they enabled this
                            feature in the whidbey.

                            "Scott M." <s-mar@BADSPAMsnet .net> wrote in message
                            news:evkidMI5DH A.2740@TK2MSFTN GP09.phx.gbl...[color=blue]
                            > Ok, thanks Jay.
                            >
                            >
                            > "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_MVP @msn.com> wrote in message
                            > news:%23$Xi7cG5 DHA.360@TK2MSFT NGP12.phx.gbl.. .[color=green]
                            > > Scott,
                            > > That does not cause the line you change to be dynamically recompiled...
                            > > VS.NET 2002 & VS.NET 2003 will force to stop, compile & then rerun your
                            > > program.
                            > >
                            > > Edit & Continue is the VB6 feature that when you stop at a break point[/color][/color]
                            you[color=blue][color=green]
                            > > can modify the source, and the modification is immediately reflected in[/color]
                            > any[color=green]
                            > > statements that you then execute.
                            > >
                            > > Hope this helps
                            > > Jay
                            > >
                            > > "Scott M." <s-mar@BADSPAMsnet .net> wrote in message
                            > > news:%23jOyr7F5 DHA.504@TK2MSFT NGP11.phx.gbl.. .[color=darkred]
                            > > > Isn't Edit & Continue already in VS.NET 2002?
                            > > >
                            > > > Tools...Options ...Debugging... .Edit & Continue...Allo w Me To Edit VB[/color][/color]
                            > Files[color=green][color=darkred]
                            > > > While Debugging
                            > > >
                            > > >
                            > > >
                            > > > > Also, with the return of edit and continue in the next version[/color][/color][/color]
                            of[color=blue][color=green][color=darkred]
                            > > > > VS.NET, I imagine that a lot of VB'ers will be very, very happy.
                            > > >
                            > > >[/color]
                            > >
                            > >[/color]
                            >
                            >[/color]


                            Comment

                            • Lord Crc

                              #15
                              Re: Choosing a programming language for use in the future...

                              On Mon, 26 Jan 2004 23:42:12 +0100, "phoenix" <patient0@skyne tWORK.be>
                              wrote:
                              [color=blue]
                              >Try manipulating the bits of a bitmap in VB.Net and you will notice what I
                              >mean. But unless you're interested in graphic stuff like that (and maybe
                              >some advanced math routines), unsafe code doesn't really have that much use.[/color]

                              You can still get pretty decent performance with safe code if you
                              access stuff on a scanline basis (which is what you usually do when
                              doing stuff like that). And no im not talking about Get/SetPixel

                              - Asbjørn

                              Comment

                              Working...