CT-044 – Módulo 5 Component Design

1. CT-044 – Módulo 5Component Design

2. Component Design • Designing a Component • Component Characteristics • Packaging (img) • Location (where in the logical tier the components belong) • Type (could be a library of code, a custom Web control, or custom Web part, etc)

3. Packaging

4. LifeCycle • The life cycle of a component is simply taking into account the construction, lifespan, and destruction of the functionality you need. • Some components are created and live for long durations, and others perform functional tasks that have very short lifespans. • Determining the component’s life cycle is critical to its design.

7. Expressing the Design • Once you have an idea of what your component design will be, you must be able to capture that design in a way that can be communicated to others. This includes creating activity, sequence, and class diagrams of your component as well as, possibly, pseudocode to represent examples of how the component will be used.

11. Lab: Component DesignBook 70-547 Page 252

12. Component Interface • Working with components is simply a conversation between two objects inside the .NET Framework Common Language Runtime (CLR), also called the .NET runtime. • The interface for a component includes the constructor, methods, properties, and events of a component. • The interface for a component is not necessarily an interface in the .NET sense. It may be a simple .NET class or it may be complicated, using interfaces, abstract, or even a Web service.

13. Interface Design • Consumers of the Component • Local, Remote, etc. • Component Lifetime Interface (table) • Singleton, singlecall, instance reference • Constructors • Finalizers

15. Lab: Component InterfaceBook 70-547 Page 261