When implementing an interface on a class, using VB.NET, the VS2010 and earlier IDE auto-generates the code based on the Interface.

I would like to suggest to have the code generated respecting the order of declaration on the Interface. I usually declare Properties first, Events after and finally the methods. Its a pain having to reorganize my code every time I create a new class and implement an interface. This is specially problematic when we have interfaces with many members.

To work around this issue I usually keep a sample of the interface implementation somewhere so I can just copy it to save some precious time.

One thing that could be quite neat would be to have a simple syntax for array operations (similar to excel array formulas):
If A and B are two collections of integer, something like
Dim C = {A + B}
Where C would be a collection = to the sum element by element of the collections A and B. With this syntax we should be able to do any operation applicable to the individual datatype. Something like
Dim A() as string = ....
Dim B = {A}.ToUpper.SubString(2) ' B would be an array of string where each element B(i) = A(i).ToUpper.SubString(2)
I.e. without having to create lambda expression (which most often are only there to do a single task anyway).

I presume that an additional flag could allow to do it in parallel (like Parallel.Foreach).

' current
Function myCompute(ByVal j As Integer) As Double
myCompute = 3.87 * j
' Disadvanteges:
' - the function name can be confused with a variable name
' - difficult to maintain when function name changed
End Function

' current
Function myCompute(ByVal j As Integer) As Double
Return 3.87 * j
' Disadvantege:
' - the Return statement is a jump statement (not structured) like: GoTo or Exit
End Function

' proposed
Function myCompute(ByVal j As Integer) As Double
Function = 3.87 * j
' Advanteges:
' - better reading and maintaining
' - not a jump statement
' - no need new VB keyword
End Function

A new casting operator that works on type instances as well as types would be very useful and enable scenarios that are not currently available in VB

Casting an Instance of a type to another type would be expanded:

<CastType>Instance
The new casting operator should operate like tryCast (return nothing if the instance is nothing or a casting error is encountered) but it should be able to cast all types, not just classes and structures.

Types themselves could be cast into compatible types
<CastType>Type
For example the type myClass implements the Interface myInterface which has a shared member

public Interface myInterface
Shared Function Parse(value as string) as SELF
myFunction2
end interface
The SELF keyword would indicate that the type that implements the Parse function would return itself

Class MyClass
implements myInterface

public shared function Parse(Value as string) as myClass implements myInterface.myFunction
end function

end class

We could then have
Dim NewObject as myClass = <myInterface>myClass.Parse("hello")

This would be very useful in factory patterns that could be implemented across many types with a unified syntax specified in an interface.

I use delegates sometimes, but not often. And most of times, while looking at C# samples, I forget to use AddressOf operator. That usually brings me a very cryptic message, which means that something is not OK with the address (delegate) of the function I want to be used for a particular purpose and I usually try to fix type of parameters of supplied function etc. before I realize that I should have used AddressOf, This was so much more hard to me when I was a .NET beginner. So, I suggest that the error message - whenever a delegate should be used and AddressOf is not supplied and given function does not return a delegate - include a suggestion to use AddressOf (and only if it is included then start emitting other error messages, about parameter types and count etc.)

After my C# idea, I would like to suggest similar Range and Between ternary operators for the VB.net also:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2591768-add-range-operator
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2591770-add-between-operator

Using of Range and Between operators:
Dim b As Boolean
b = 5 In 5 To 9 'True
b = 5 In 5 >< 9 'False

Why would useful these ternary operators?
The Range and Between operations are used very often but their present usage is not safe:
b = X >= 5 And X <= 9
b = X > 5 And X < 9

In both cases, the variable X is used twice what is not safe.
The redundant typing and maintenance can cause a wide variety of mistakes.
A further problem may be that the comparison operators are also required to use twice.
I think all programmers have encountered such mistakes:
b = X >= 5 And X < 9
b = X > 5 And X > 9

In addition, the present way is also not strict with the operation order which can cause a bad readable code:
b = X <= 9 And X >= 5
b = X < 9 And X > 5

The above problems would happen far less often or never with the 'In' operators:
b = X In 5 To 9
b = X In 5 >< 9

Advanteges:
- safer
- stricter
- simpler
- shorter
- easier to read
- easier maintenance
- intelliSense would be supported
- not need new reserved keywords

Some other examples:
b = 5 In 5 =>< 9 ' *** True
b = 5 In 5 ><= 9 ' *** False

b = 5.0 In 5.0 To 9.0 ' *** True
b = 5.0 In 5.0 >< 9.0 ' *** False
b = 5.0 In 5.0 =>< 9.0 ' *** True
b = 5.0 In 5.0 ><= 9.0 ' *** False

b = myDate In dte1 To Now()
b = myDate In dte1 >< Now()
b = myDate In dte1 =>< Now()
b = myDate In dte1 ><= Now()

If strLastName In strName1 To strName2 Then MsgBox("From-To")
If strLastName In strName1 >< strName2 Then MsgBox("Between")

more related topics:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2406718-using-logical-and-operator-in-the-select-case-stat
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2406727-using-between-operator-in-the-select-case-statemen

The QLike (Query Like) operator should work same way as the Transact-SQL Like operator:
http://msdn.microsoft.com/en-us/library/ms179859.aspx

Dim b As Boolean
' The following statements return True
b = "A" Like "A"
b = "A" QLike "A"

' The following statements return False for Option Compare Binary
' and True for Option Compare Text
b = "A" Like "a"
b = "A" QLike "a"

' The following statements return False
b = "A" Like "AAA"
b = "A" QLike "AAA"

' The following statements return True
b = "aBBBa" Like "a*a"
b = "aBBBa" QLike "a%a"

' The following statements return True
b = "E" Like "[A-Z]"
b = "E" QLike "[A-Z]"

' The following statements return False
b = "E" Like "[!A-Z]"
b = "E" QLike "[^A-Z]"

' The following statements return True
b = "a2a" Like "a#a"
b = "a2a" QLike "a[0-9]a"

' The following statements return True
b = "aM5b" Like "a[L-P]#[!c-e]"
b = "aM5b" QLike "a[L-P][0-9][^c-e]"

' The following statements return True
b = "BAT123khg" Like "B?T*"
b = "BAT123khg" QLike "B_T%"

' The following statements return False
b = "CAT123khg" Like "B?T*"
b = "CAT123khg" QLike "B_T%"

The QLike operator could be used with the Select Case statement also:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2406694-using-like-operator-in-the-select-case-statement