I faced this issue today. I wanted to call a function written in C# from my VB.NET code, but I found out that the coder of the library had not followed Microsoft guidelines for interoperability and had used same name for two functions differing only by case having the same signature. I didn't have access to the C# code, so was helpless as VB.NET does not allow me to use any of these functions.
