D
Don
I've got a problem with two DLLs that are referencing each other. Here is
the breakdown of the problem (the identifiers I use are not the real ones):
1. DLL-One declares a Class-X.
2. DLL-Two has a public method that has a parameter of Class-X (reference to
DLL-One required).
3. DLL-One calls the public method from DLL-Two, passing it an instance of
Class-X (reference to DLL-Two required).
4. VB Gives me an error in DLL-One stating "Reference required to assembly
'DLL-One' containing the type 'Class-X'. Add one to your project.
This makes no sense because Class-X is declared in DLL-One. Why is VB
telling DLL-One that it needs a reference to itself? Aside from creating a
new DLL to store Class-X or merging everything into one DLL, how can I fix
this? I don't even understand why I'm getting the error. Any help would be
greatly appreciated.
- Don
the breakdown of the problem (the identifiers I use are not the real ones):
1. DLL-One declares a Class-X.
2. DLL-Two has a public method that has a parameter of Class-X (reference to
DLL-One required).
3. DLL-One calls the public method from DLL-Two, passing it an instance of
Class-X (reference to DLL-Two required).
4. VB Gives me an error in DLL-One stating "Reference required to assembly
'DLL-One' containing the type 'Class-X'. Add one to your project.
This makes no sense because Class-X is declared in DLL-One. Why is VB
telling DLL-One that it needs a reference to itself? Aside from creating a
new DLL to store Class-X or merging everything into one DLL, how can I fix
this? I don't even understand why I'm getting the error. Any help would be
greatly appreciated.
- Don