> I figured out that the problem arose from the fact that my interface was > both implemented both in a specific assembly AND in the generated dll. The > compiler always took the interface in the dll - so the compiler says - and > BANG. Do you happen to know how to tell VS.NET what assembly to take > during > compilation when there are two definitions with identical names in two > separate assemlbies?
Use namespaces. :p The C# and VB.NET compilers are totally brain-dead when it comes to letting you specify the assembly part of a type's identity. This can lead to problems. [1] [1] http://staff.develop.com/candera/clrversion.htm You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
