Managing loosely coupled assembly references incurred through usage of the 'Designer' attribute?

Why not create a single designer that uses something like the Managed Addin Framework or Activator. CreateInstance internally to pick and show a designer? With this technique, the Designer attribute would never have to change...

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.