Thank you Sijin.
So the linking process at build time will locate the interface because it
has been referenced and resolve the contract between the interface and the
class that implements the interface.
What is the reason for moving the interface into a separate project? I am
guessing it has something to do with not being bound to the
component/assembly which it is describing?
Thanks again!
-Greg
"Sijin Joseph" <si*********@hotmail.com> wrote in message
news:OI*************@TK2MSFTNGP09.phx.gbl...
If possible move the interface into a seperate project. In the projects
that implement the interface, add a project reference to the interface project.
--
Sijin Joseph
http://www.indiangeek.net
http://weblogs.asp.net/sjoseph
"Hazzard" <ha**@sonic.net> wrote in message
news:%2***************@tk2msftngp13.phx.gbl... If I have two assemblies in a VSNET project and create an interface,
does the interface have to reside in the assembly whose class methods it
describes?
How do I reference interfaces in the project?
Are there any good articles that describe interfaces from a good
functional/operational/Visual Studio .NET point of view?
I am working on a multi-project solution whose references are a
combination of project references and file references. Throw in a circular reference
with the need to create late bound objects, and it makes for an
interesting challenge.
appreciatively,
hazz