Component Class Vs Class

[Rhys666]

To keep this short, and because I've asked similar in the ASP.net forum with a startling lack of response and don't want to cross post the same question entirely, does anyone have any experience with Component classes who can provide a brief overview of their benefits and drawbacks in comparisson to standard Classes, especially when being used in ASP.net (c#).

This is relavant to a project I'm currently working on and my understanding of the two as I feel Component classes are more heavyweight than a standard Class and not really necassary unless utilised within the design environment for simplicity and re-usability sake.

Rhys

""Vampireware /n/, a project, capable of sucking the lifeblood out of anyone unfortunate enough to be assigned to it, which never actually sees the light of day, but nonetheless refuses to die."

My Home

 

[stsuing]

Component Classes are for people that don't know OO and don't want to type everything. The code generated always seems more wordy then what I create myself because the generator doesn't know the exact usage of the component and has to over-engineer everything. Personally I think there useless and leave me with the sense that I don't know all that is going on in my class.

 

[JohnYingling]

The namespaces in the .NET Framework for creating your own components and controls include:

System.ComponentModel - provides classes that are used to implement the run-time and design-time behavior of components and controls. This namespace includes the base classes and interfaces for implementing attributes, working with type converters, binding to data sources, and licensing components. The classes in this namespace divide into the following categories: "

http://www.VBCompare.com

Compare Code

 

[Rhys666]

John,
I know (or believe I know) the technical differences, I'm asking about real-world experience and observation, before I decide whether to voice some constructive critisism of company methodology as they use component classes for all data classes, with typed datasets etc, where as my natural preference would be for, (what I consider to be), more lightweight standard classes without the vis. studio added bumf.

Rhys

""Vampireware /n/, a project, capable of sucking the lifeblood out of anyone unfortunate enough to be assigned to it, which never actually sees the light of day, but nonetheless refuses to die."

My Home