为什么混合VB.Net和C＃在同一个解决方案，不建议？ [英] Why is mixing VB.Net and C# in the same solution not recommended?
问题描述
I was reading this question when I noticed a curious comment underneath:
不知道问题是什么。你可以在一个解决方案中使用VB.NET和C＃项目（虽然我不建议这样做）
not sure what the question is: you can use VB.NET and C# projects in one solution (though I wouldn't recommend doing so).
我这个做了不少，因为我们有传统的VB.Net代码，新代码是用C＃。这是真的不推荐？为什么不呢？
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?
推荐答案
有没有真正的理由，以避免这一点，除了从一个解决方案两门语言增加复杂性
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.
这篇关于为什么混合VB.Net和C＃在同一个解决方案，不建议？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
