tags:

views:

107

answers:

5

I have searched for these and can only find posts on 2008 or earlier?

I have my own list, but I want to know if there are more?

  • Vb.NET doesn't support implicit interfaces (this really is annoying:()
  • Vb.NET doesn't support another setter protection than the getter on automatic properties
  • Vb.NET doesn't support Preprocessor Directives
  • Vb.NET doesn't support Arithmetic Overflow unchecking/checking in code
  • Vb.NET doesn't support the yield keyword (iterator blocks)
  • Vb.NET doesn't support execution of unsafe (i.e. pointer-based) operations.

And then we have the support for the environments like type coloring which is still poor in vs.net 2010 and not full support from resharper and so on but that is not any technical aspect. Have i missed something?, I have heard that there could be some differences in linq querying is that true?

+1  A: 

VB.net supports XML-Integration, C# does not

VB.Net:

Dim xmlTree1 As XElement = _
    <Root>
        <Child1>1</Child1>
        <Child2>2</Child2>
        <Child3>3</Child3>
        <Child4>4</Child4>
        <Child5>5</Child5>
        <Child6>6</Child6>
    </Root>

versus C#:

XElement xmlTree1 = new XElement("Root",
    new XElement("Child1", 1),
    new XElement("Child2", 2),
    new XElement("Child3", 3),
    new XElement("Child4", 4),
    new XElement("Child5", 5),
    new XElement("Child6", 6)
);
dkson
A: 

Making a component that can be called from COM is very easy in VB.Net. In C# it is almost impossible.

Johann Strydom
To all the people who have down voted me: Have you even tried doing it?
Johann Strydom
No vote from me, -2 is about enough. But, yes, it is trivial. Mostly because it is done the *exact same way*. Maybe you ought to ask a question about it...
Hans Passant
A: 

Probably lots more, but in my day to day work these are the ones that annoy me the most (I can't abide VB.Net):

VB.Net has optional parameters, C# does not. C# has a mechanism to generate XML documentation from code tags. C# has the using keyword C# allows you to write unsafe (eg pointer-related) code.

hth.

5arx
C# has optional parameters now.
Johann Strydom
Are you sure about the *unmanaged* code part? Isn't that only in C++.Net?
Johann Strydom
VB has the `Using` keyword: http://msdn.microsoft.com/en-us/library/htd05whh.aspx
LukeH
@Johann Strydom unsafe code in c#: http://msdn.microsoft.com/en-us/library/chfa2zb8%28VS.71%29.aspx
dkson
Interesting. Didn't even know it could be done.
Johann Strydom
A: 

Multiline string literal with @ in C# is missing in VB.NET. Makes long strings really annoying.

alxx
A: 

C# still doesn't have exception filters...

LukeH
/me is deeply suspicious about conditional exception handling...
annakata