> C# is defining the function, having an argument of the VB > class type. I can call it from other C# classes but I cannot > get the VB compiler to call it either within or without the > same namespace.
As Thomas mentioned earlier you probably have a circular project reference then ie Project1 defines (and uses) Class1 Project2 defines (and uses) Class2 Project1 uses Class2 from Project2 Project2 uses Class1 from Project1 This cannot be done To make it obvious why..which would you compile first? You cannot compile Project1 first as it uses a Project2 class And you cannot compile Project2 first as it uses a class from Project1 The easiest way to fix this is to have a third dll that exposes the class that's being used everywhere, and reference that, ie Project1 defines (and uses) Class1 Project2 uses Class2 Project3 defines Class2 Project1 now uses Class2 from Project3 Project2 now uses Class2 from Project3 You can still place Class2 in the same namespace, but it needs to be in a project that can be referenced by both client projects Merak You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
