.NET Framework Class Library Design Question - ISite, IComponent and IContainer

[Guest]

I have copied the associated interfaces from MSDN below. The problem is that
I do not completely understand why it is designed in that way? What is ISite
for and is it really useful? And finally does anybody know new enhancements
in this design on Whidbey?

Copied from MSDN for your convenience:
public interface ISite : IServiceProvider
{
IComponent Component {get;}
IContainer Container {get;}
bool DesignMode {get;}
string Name {get; set;}
}

public interface IComponent : IDisposable
{
ISite Site {get; set;}
event EventHandler Disposed;
}

public interface IContainer : IDisposable
{
ComponentCollection Components {get;}

void Add( IComponent component );
void Add( IComponent component, string name );
void Remove( IComponent component );
}

 

[Joerg Jooss]

I have copied the associated interfaces from MSDN below. The problem
is that I do not completely understand why it is designed in that
way? What is ISite for and is it really useful?

Have a look at this article:
http://www.theserverside.net/blogs/showblog.tss?id=pluginArchitectures


Cheers,