Hi!
So far I have stumbled upon System.Componentmodel only when using some attributes and in WinForms.
But last month I had an architecture class where components played a big role, but those were not .net component types but general whiteboard things.
I am wondering what System.ComponentModel.Component really is.
So, is this some really clever stuff for developing enterprise reuse "components" in the architectural sense or just the base class for winforms controls?
What can one do with classes deriving from System.ComponentModel.Component that one can't do with a normal class?
Maybe there's a little pearl hidden in this namespace that I have missed these last nin years of .NET development?
I've read What is System.ComponentModel Namespace? but it didn't sound particularly impressive.
Lots of Greetings!
Volker