Using Microsoft.VisualBasic from C # and VB.NET has been discussed in detail in this matter . The Microsoft.VisualBasic namespace is fully supported , and will work as long as .Net is nearby. There is no reason to avoid it.
EDIT:. Saying that during input, the other answers to this question are an incorrect re-evaluation of the function and an unsupported library from the one-person code gallery. Come on guys, this will take the real main event for Microsoft to give up the financial functions of VB.
This is another story for Microsoft.VisualBasic.Compatibility , which is intended solely for use by the VB6 update wizard, EDIT is now marked as deprecated in .Net 4 (my prediction came true), and it cannot be used for new development. There would be some advantages in eliminating the links to this, but personally, I will probably try to create a fully working port that first references .NET 3.5.
Markj
source share