Prashant, your post is a tad misleading:
Quote:
quote:Originally posted by Prashant.k.m
But C# is a totaly new language designed to .Net Platform, it is strongly typed and bit more options than vb.net.
|
VB.NET is also designed for the framework. It is strongly typed. All languages that work in .NET must work with the framework. True, C# does have a few more tricks up its sleave that
VB.NET does not, but not that many.
The Microsoft.VisualBasic namespace has many functions that are found in earlier version of
VB to support migration. However, many of those functions can be found in a similar form in the framework, and I'd recommend learning those in order to stick to generic framework methods (vs. language specific). If you still need to use some older style
VB function, you can. And you can use them in any .NET language because the Microsoft.VisualBasic classes are part of the framework.
Quote:
quote:
Also the case insensitivty may cost a bit to the CLR in case of VB.net.
|
When .NET code is compiled, it's all distilled down to MicroSoft Intermediate Language (MSIL) that lives in the assembly (DLL/EXE). This makes the case issue irrelevant when it comes to performance.[/quote]
Avanish-
Until you get into advanced coding techniques where you may need to take advantage of some of the minor differences between the .NET languages you will find that they both perform and behave the same. All .NET languages support all aspects of the framework while each provides a few things the others don't.
-
Peter