vb.net - Would you develop in VB and then convert your code to C# just to have your entire team use one language? -


I'm not considering this - I'm comfortable with C # and VB, but neither an expert but, Some of my team has expressed the intention to do this because we are moving towards C # as a standard.

Hell's no no just a complete waste of time.

I will use VB on C # (or C # VB) only if language enabled functionality which was not available in other.

For example, VBs are much easier for CC interop objects to be discontinued when compared to late calls in C # (though this is converting to C # 4.0).

It is being said, I would like to be with the language that your team is using, or whatever you like (if that is an option).


Comments