Jay Kimble

All three will call newobj to create a new instance of the object and return and memory address to store on the stack.  However, the C# compiler is a bit more intelligent about the use of an object at compile time.  If it sees that you don't use the Obj variable, it actually won't get created and the reference to the object will just get popped back off the stack, meaning Obj will never exist.  The VB compiler doesn't do this and will actually assigned the memory address to the variable Obj, even though you may never use it.  Really, without seeing the context in which you wish to implement the line of code you have shown us, the MSIL will look different surrounding these statements.  But I think the answer you were looking for is "they all look identical as far as the newobj instruction in IL".

Ok lemme do another Sahil thing -

"So whats the answer man :-P"

Blue code is always more efficient thatn green code. Therefore, since you used green fonts for C#, it will be more efficient. (he he he).

It's all the same thing to the Framework.  But the C# code still gets paid more.

Doesn't "Dim Obj as new aClass()" have some sort of side effect?  Or has that been eliminated.  I think if you used that syntax in VB6, you could have unintended consequences - the object would be created whenever it was referenced.  So if you had:

Set Obj = Nothing

in some cleanup code, even if the Obj had already been deleted, it would be created again and then set to Nothing.

It is completely possible I am making all of this up.