I was doing some development using Interface model for other
developers to drop their dll anytime so that my code can consume their
implementation when required. I was told, in C# 3.0 there is a feature
called addin/addon that can do the same with out most of these fuss.
Does anyone know anything about this? I googled couldn't find anything
or may be I am not looking for correct informaiton??
Thanks,

On May 5, 11:03*am, CSharper <cshar...@gmx.com> wrote:
> I was doing some development using Interface model for other
> developers to drop their dll anytime so that my code can consume their
> implementation when required. I was told, in C# 3.0 there is a feature
> called addin/addon that can do the same with out most of these fuss.
> Does anyone know anything about this? I googled couldn't find anything
> or may be I am not looking for correct informaiton??
> Thanks,

there is onthing like that. You need to define an interface in a
separate dll and the developers need to implement that interface.
Additionally you could use reflection to discover dynamically what
method to call

On May 5, 8:03*am, CSharper <cshar...@gmx.com> wrote:
> I was doing some development using Interface model for other
> developers to drop their dll anytime so that my code can consume their
> implementation when required. I was told, in C# 3.0 there is a feature
> called addin/addon that can do the same with out most of these fuss.
> Does anyone know anything about this? I googled couldn't find anything
> or may be I am not looking for correct informaiton??

In 3.5, there's namespace System.AddIn. You can read more about that
here:

http://msdn.microsoft.com/en-us/magazine/cc163476.aspx

Now, it's a very powerful thing, including sandboxing capabilities,
but sometimes you may find it to be overkill for your particular task,
and the extra complexity to not worth it. In which case another, more
lightweight option is Managed Extensibility Framework (MEF):

http://www.codeplex.com/MEF

Note that, while it's not part of the .NET framework proper (so you'll
have to redistribute the assemblies), it's still a Microsoft project.