Why is mixing VB.Net and C# in the same solution not recommended?

Question

I was reading this question when I noticed a curious comment underneath:

not sure what the question is: you can use VB.NET and C# projects in one solution (though I wouldn't recommend doing so).

I do this quite a bit, as we have legacy VB.Net code, and new code is written in C#. Is this really not recommended? Why not?

Answer 1

There is no real reason to avoid this, other than adding complexity from having two languages in one "solution".

Your scenario (working with a legacy product, but adding new features) is a valid reason to have both languages used in a single solution, in my opinion.