Modularity is the separation of an application in independent and collaborative modules. You use modules to encapsulate a set of concerns of your application and independently develop and deploy them to your applications. The following topics explore further
concepts about modularity.
- Composite Web Client Applications. This topic introduces the concept of a composite Web client application. It explains
the use of shell modules, which provide the overall user interface structure, and how they interact with other modules. It also explains how composite applications are particularly well suited for service-oriented architectures (SOA).
- Composite Web Application Block. Building composite Web client applications with the Composite Web Client Automation requires
that you use the Composite Web Application Block. This topic explains how the application block promotes the use of modularity and the benefits that result from this practice.
- Modularity Patterns. This topic discusses the Inversion of Control pattern, the Dependency Injection pattern, and the Service Locator
pattern. These patterns provide possible approaches to building composite applications. The topic includes discussions of the benefits and limitations of the three patterns.
Application blocks help address the common problems that developers face from one project to the next. They are designed to encapsulate the Microsoft recommended best practices for .NET-based applications. To fully understand the modularity guidance in this
bundle, you must be familiar with the Composite Web Application Block.