Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is anybody could explain when and why we should use System.ComponentModel.Container, please? Recently I have met using of this class here, but really cannot understand what a benefit can get us this class there.
In general,
System.ComponentModelnamespace exists for supporting component development – components can be visual (controls) and non-visuals. IMO, one should develop Components (in this contextIComponentimplementations) when design time support is needed. For example, you can drag Components on to the design surface in Visual Studio and access their properties. In this context,IContainer&Containerrepresent a holder that will contain one or more components. I seriously doubt if you need to useSystem.ComponentModel.Containerdirectly – this class would be used by .NET framework and Visual Studio (or other designer tools) internally. As far as, the code that you have sighted, it appears to be quite outdated and for that matter, it is not even instantiating Component class (just a reference is created).