By joining Download. Free YouTube Downloader. IObit Uninstaller. Internet Download Manager. Advanced SystemCare Free. VLC Media Player. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Biden to send military medical teams to help hospitals. N95, KN95, KF94 masks.
GameStop PS5 in-store restock. Baby Shark reaches 10 billion YouTube views. Microsoft is done with Xbox One. Windows Windows. Most Popular. New Releases. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. What Is a Software Factory? One of the first steps in building a long-lived ASP. NET project is to define standards for how to use the many features of the platform. Without such standards, it is easy for the project to degenerate into a jumble of different development techniques and styles.
One developer may use Master Pages extensively in her part of the project, for example, while another favors nested user controls. The end result is a tangle of different techniques applied across the application, making it difficult to make high-level architectural decisions or changes.
Enforcing these standards for developing applications can be difficult, however, due to the lack of tools. If you decide on a set of standards that are not directly supported by the normal tools within your development environment, you have to either build your own tools or create very specific instructions for developers to follow when performing certain tasks.
It created a toolset designed specifically for the task of building large Web sites with ASP. NET that are worked on by many developers concurrently. Before I delve into the details of what the Web Client Software Factory provides, it makes sense to describe what a software factory is. It creates packages of tools, documentation, and reference implementations for product groups that are intended as guidance for how to best use a particular technology in an enterprise environment. Instead of starting with the somewhat low-level Web service features exposed by the WCF libraries, the Web Service Software Factory provides guidance and tool support for creating message-based systems that follow commonly used patterns of design and are built for longevity, interoperability, and maintainability.
Similarly, there are software factories for smart clients, mobile clients, and Web clients—the focus of this column. While a software factory may sound like a single component you could incorporate into a project, it actually describes an entire collection of assets you can use in developing applications with a specific technology. Each of the software factories available contains:. NET, and it addresses many of the architectural concerns outlined in the introduction. Each of these application blocks comes with a collection of recipes and templates that extend Visual Studio, a full set of how-to documents describing specific tasks along with descriptions of the patterns involved with each, and a complete reference implementation of an e-banking site that uses both application blocks to their full extent.
For the remainder of this column, I will focus on the composite application block, both to narrow the scope of the topic and also because I think developers will find it the most immediately compelling. Once you have installed the Web Client Software Factory installation binaries and complete instructions for setup can be found at codeplex. The first thing you will notice about the solution that is created with the Web Client Development Guidance Package project, shown in Figure 2 , is that it is split into two distinct projects: a library project called Shell listed under a directory called Modules, and a Web site called DevelopmentWebsite listed under a directory called WebSites.
These are actually just the first two of several projects you will add to your application with the goal of creating multiple independent modules that all work together to define a single Web site. The general layout of this solution is to create a separate module class library project for each section of the site. Each module will be independently compilable and will have a separate directory of pages and codebehind files in the main Web site directory.
The goals of this project layout are to make it feasible for multiple developers to work independently on different portions of the site without interfering with each other and to be able to deploy modules independently by pushing out a new binary and a fresh directory of pages to the deployment server without redeploying all modules together.
In order to prepare for multiple modules to be incorporated into a single site, the Web Client Solution project template implicitly makes several decisions about the structure of the Web site. This Master Page by default contains a tree view control tied to a SiteMapDataSource to display the navigable pages on the site as well as a SiteMapPath control to display the current location with breadcrumb links back up the tree. There are several other pieces of infrastructure put in place by the project template, which you will notice as you poke around the generated files.
Most of these are in anticipation of managing multiple modules or have to do with the authorization features of this application block. For example, you will notice in web. One of the core benefits of working with the Composite Web Application block is the ability to split a site into multiple independent modules. As mentioned before, each module is responsible for a subdirectory in the main site and all of its content. Figure 3 shows the elements that will be added using this template with a new business module named Customers.
This recipe creates a new top-level subdirectory in your Web site with the same name as the business module, as well as a new class library project under the Modules directory.
Initially it contains a definition for a presenter class DefaultViewPresenter and an interface IDefaultView , defining methods for the View to be implemented by the Default. A top-level Controller class is also defined in the project that combined with the view and presenter classes will complete the page logic for this module.
The last piece of interest is the CustomerModuleInitializer. This class defines initialization methods that will be called as the Web site first loads, and it gives the module an opportunity to initialize any data, register site map information, and so on. There is also a recipe for adding a new foundational module to your application rather than a business module , which creates a new class library project complete with a ModuleInitializer class but without any explicit correspondence to a directory or page within the Web site.
This can be useful for supplemental business logic that does not tie directly to any particular set of pages in the site.
0コメント