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

[murl]

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

 

[Nicholas Paldino [.NET/C# MVP]]

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.

 

[Chad Z. Hower aka Kudzu]

(e-mail address removed) (murl) wrote in @posting.google.com:

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

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/
"Programming is an art form that fights back"


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

 

[Jose Caliente]

lear C# !

jc

(e-mail address removed) (murl) wrote in @posting.google.com:

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/
"Programming is an art form that fights back"


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

 

[Herfried K. Wagner [MVP]]

lear C# !

???

 

[phoenix]

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

 

[Murl Brown]

Ok, well thanks for the advice, i will still continue to study c# and
integrate it slowly into future apps i use, but will stick mainly to
vb.net cause if what you say is true about performance issues being
somewhat the same, and that it is a language preference, then i'll stick
with what i know.

 

[Scott M.]

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

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

 

[Guest]

I have studied vb6, vb.net, and c++, and am currently learning

alot about c#

if you know C++ and also learning a lot with C#, i think you should stay and continue sharpening your C Sharp skills. (since you already know VB.NET)

 

[Jay B. Harlow [MVP - Outlook]]

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

 

[Bram]

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.

 

[piddie]

(e-mail address removed) (murl) wrote in

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

Not true.

I found this...

"... 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.

 

[Scott M.]

Ok, thanks Jay.

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.]

Knowing VB 6.0 is not the same as knowing VB.NET

if you know C++ and also learning a lot with C#, i think you should stay

and continue sharpening your C Sharp skills. (since you already know VB.NET)

 

[Abubakar]

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

 

[Lord Crc]

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.

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

 

[Cor]

Hi Nicholas,

That was the answer, can add nothing.

The discussions had result.

)

Cor

 

[Herfried K. Wagner [MVP]]

if you know C++ and also learning a lot with C#, i think you should
stay and continue sharpening your C Sharp skills. (since you already
know VB.NET)

I would learn both, VB.NET and C#.

 

[Herfried K. Wagner [MVP]]

Knowing VB 6.0 is not the same as knowing VB.NET

But it makes learning VB.NET easier than learning C#.

;-)

 

[Scott M.]

True, but that's not my point. The last post said "you already know
VB.NET", implying that if you know VB 6, you know VB.NET and my post was
pointing out that this is not true.