Proj layout: where to define an interface

[ChrisA]

I have an asm that implements an interface. Since the asm will be loaded
dynamically, where should the interface be defined so that the client and
implementation can both use it? It seems like over-kill to define a shared
asm that just contains the interface definition. If the inteface is defined
in a shared project file, can there be a versioning issue?

[Carlos J. Quintero [.NET MVP]]

Take into account that an interface is a type, and a type is not only a name
(or a full name with namespace). The type identity includes also its
assembly. So, the interface must reside in a shared assembly, not in a
shared project file. The shared assembly can be the one with the
implementation as long as you don´t change the full name of the assembly,
and that includes the assembly version (AssemblyVersio n attribute, set fixed
to, say, 1.0.0.0). You can change the AssemblyFileVer sion attribute to
distinguish your compilations, though, since it is a different concept of
version. Otherwise, the shared assembly should contain only the definition.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"ChrisA" <Ch****@discuss ions.microsoft. com> escribió en el mensaje
news:A4******** *************** ***********@mic rosoft.com...

I have an asm that implements an interface. Since the asm will be loaded
dynamically, where should the interface be defined so that the client and
implementation can both use it? It seems like over-kill to define a
shared
asm that just contains the interface definition. If the inteface is
defined
in a shared project file, can there be a versioning issue?