c#-to-vb.net

I have a team with people that are quite comfortable in C# but we got a requirement to write a project in VB.net. How hard would it be to think in C# and on the fly convert to VB? Is that doable? Could you list the issues that we can come across? I heard that VB.net doesn't have closures. Is that still true for .net 3.5? If you are approaching VB.Net with the mindset of C# it's best to set the following options in the project Option Strict On Option Explicit On Option Infer On This essentially removes the late binding semantics of VB.Net and forces it to be a strictly typed language. This will

After debugging a particularly tricky issue in VB.NET involving the order in which instance variables are initialized, I discovered that there is a breaking discrepancy between the behavior that I expected from C# and the actual behavior in VB.NET. Nota bene: This question concerns a slight discrepancy in the behaviors of VB.NET and C#. If you're a language bigot that is unable to provide an answer other than "that's why you should use C#, noob" , there is nothing for you to see here; kindly move along. Specifically, I expected the behavior outlined by the C# Language Specification (emphasis

Does VB.NET have a direct equivalent to C# out function parameters, where the variable passed into a function does not need to be initialised? No, there is no equivalent of the out keyword in VB. However, VB does automatically initialise all local variables in a method, so you can use ByRef without needing to explicitly initialise the variable first. Example: Sub Main() Dim y As Integer Test(y) End Sub Sub Test(ByRef x As Integer) x = 42 End Sub (If you examine code in the framework (for example Double.TryParse ), you may see the <OutAttribute> added to parameters, but that only makes a