Ravichandran J.V. said:
VB.Net is extensively supported in the VS.Net environment with help like
case-insensitive coding, drop-down menus, easy to use declaration of
event procedures etc while, C# is not so well-supported.
I'm not sure I'd say that case-insensitive coding is a help, myself -
and Intellisense can correct your case if you like.
There are drop-down menus for types and members in the C# editor, but I
agree there are more in VB.NET.
Personally I don't like the declarative form of event handling, but
that's a whole other discussion.
C#, as an OO language, provides for a class member called the class
indexer, while VB.Net does not.
Yes it does:
Option Strict On
Imports System
Public Class Test
Public Default ReadOnly Property Foo(ByVal i As Integer) As Integer
Get
Foo = i*2
End Get
End Property
End Class
Then from C#:
using System;
class Foo
{
static void Main()
{
Test t = new Test();
Console.WriteLine (t[5]);
}
}
In fact, it's C# which is the "odd" one here - the CLR just knows an
indexer as a property with parameters and the appropriate
DefaultMemberAttribute applied to the type.
C# also provides for XML documentation while VB.Net does not.
True, although there are add-ons you can use to get over that, of
course.
