These 3 languages (along with future .NET languages) share the same functionality, speed, runtime, objects/data types, their all object orientated, and they all compile the same way.
Is there any point in learning more than one .NET language?
Printable View
These 3 languages (along with future .NET languages) share the same functionality, speed, runtime, objects/data types, their all object orientated, and they all compile the same way.
Is there any point in learning more than one .NET language?
Most things you do in one language can be done in the other languages. There are however some things that are not supported in one language that are in the others. Learning .Net isn't really learning a language, that is just syntax, you are really learning the framework and how the CLR operates.
I would say pick one that has the syntax you perfer and go with it. If your used to VB, then VB.Net will probably be the easiest syntax for you to pick up on and go with. If your used to java or C++, maybe C# or C++ will be the language for you.
I find it is great for me to learn both VB.Net and C#, since all the examples I have seen are in either of those two languages. I can easily convert samples between the two now to apply it to the language I am using.
I've already learned VB.NET, and have a pretty good understanding of the .NET framework.Quote:
Originally posted by hellswraith
Most things you do in one language can be done in the other languages. There are however some things that are not supported in one language that are in the others. Learning .Net isn't really learning a language, that is just syntax, you are really learning the framework and how the CLR operates.
I would say pick one that has the syntax you perfer and go with it. If your used to VB, then VB.Net will probably be the easiest syntax for you to pick up on and go with. If your used to java or C++, maybe C# or C++ will be the language for you.
I find it is great for me to learn both VB.Net and C#, since all the examples I have seen are in either of those two languages. I can easily convert samples between the two now to apply it to the language I am using.
Although I havn't learned C#, I can easily read/understand examples written with it.
What I'm wondering is: Under what circumstances would one .NET language be more useful than another? Is basic syntax the only difference between the .NET languages?
Umm I'm not a pro in these things, but C# and VB.NET are pretty much the same thing.... But C++.NET is different from these two. I think it is also better when it comes to performance....
There is VERY little difference besides the syntax. Between VB and C#, this is all I could find on the web:
Unsafe Blocks (C#)
using (C#)
Documentation Comments (C#)
Operator Overloading (C#)
Late Binding (VB)
I am sure there are a few more, but probably not much.
Here might be a big one though, MS has submitted C# to a standards body who approved the new standard. Mono is probably the most well known effect of this... http://www.go-mono.com/
In a nutshell, other people besides MS can create compilers for C# that will allow you to write your apps for other OS's...if the people can do it right. Can't say that about VB.Net...
Oh, and if you write code in C++ for the .Net framework, then it won't be any faster than VB and C#, only because it all gets compiled to the same IL.
Ahh! This is interesting.Quote:
Originally posted by hellswraith
Here might be a big one though, MS has submitted C# to a standards body who approved the new standard. Mono is probably the most well known effect of this... http://www.go-mono.com/
In a nutshell, other people besides MS can create compilers for C# that will allow you to write your apps for other OS's...if the people can do it right. Can't say that about VB.Net...
I'm surprised Microsoft isn't against Mono. Somehow, I am. I feel that if the .NET platform becomes open-source, companies will start adding their own modifications to it, and it will no longer be standardized.
Then again, if done correctly, this could be a huge step in the right direction for developers.