| Enterprise Library (October 2008)
The patterns & practices Enterprise Library is a collection of reusable and extensible application blocks designed to assist developers with common enterprise development challenges. Enterprise Library contains application blocks for Caching, Cryptography, Data Access, Exception Handling, Logging, Dependency Injection, Security and Validation. | | Unity Application Block (October 2008)
The Unity Application Block (Unity) is a lightweight, extensible dependency injection container. It facilitates building loosely coupled applications and provides developers with simplified object creation, abstraction of requirements, increased flexibility, and service location capability. | | Team Development with Visual Studio Team Foundation Server (September 2007)
This guide shows you how to make the most of Team Foundation Server. It starts with the end in mind, but shows you how to incrementally adopt TFS for your organization. It's a collaborative effort between patterns & practices, Team System team members, and industry experts. | | Security Guidance for .NET Framework 2.0 (August 2005)
This page provides an index to the patterns & practices Security Guidance for .NET Framework 2.0 project. You can use the guidance to improve both the security of your applications and your approach to building secure applications. | | Testing .NET Application Blocks - Version 1.0 (January 2005)
Testing .NET Application Blocks covers many testing areas that were used during testing and verification of the various application blocks provided by Microsoft's patterns & practices group, such as functional, globalization, performance, integration, and security. The guide uses code examples, sample test cases, and checklists to demonstrate how to plan and implement each type of test. | | Describing the Enterprise Architectural Space (June 2004)
This document presents an organizing table that describes the enterprise architectural space, shows relationships among artifacts in the space, and demonstrates how different roles in your enterprise view enterprise architecture. This document also demonstrates how pattern authors can use this table to organize existing patterns and to identify areas where patterns are not currently documented. | | Integration Patterns (June 2004)
Integration Patterns explains how patterns were used to design and build a baseline integration architecture within a representative customer scenario. The guide presents a catalog of 18 integration patterns including implementations that use the Microsoft platform. |
| | Improving .NET Application Performance and Scalability (April 2004)
This guide provides end-to-end guidance for managing performance and scalability throughout your application life cycle to reduce risk and lower total cost of ownership. It provides a framework that organizes performance into a handful of prioritized categories where your choices affect performance and scalability success. Information is segmented by role to make it more relevant and actionable. This guide suggests processes and steps for modeling performance, as well as measuring, testing, and tuning your applications. Expert guidance is also provided for improving the performance of managed code, ASP.NET, Enterprise Services, Web services, remoting, ADO.NET, XML, and SQL Server. | | Data Patterns (June 2003)
Data Patterns extends previous patterns work by applying it to data problems and showing how to solve them by using SQL Server. These patterns are about the problems faced by those who build the data services in an enterprise class business solution. The guide introduces patterns and why they are important to database designers and administrators, as well as architects and developers. It then presents a catalog of 12 architecture, design, and implementation patterns that are organized to help you locate the right combination of patterns to solve your problem. | | Deploying .NET Framework-based Applications (June 2003)
This guide will give you the information necessary to plan and implement the effective deployment of your Framework-based applications. If your organization is developing .NET Framework-based applications, you face the challenge of deploying those applications efficiently and reliably throughout your environment. If you are experienced in the area of deployment, some of the challenges will be familiar. However, there are a number of new technologies in .NET Framework-based applications, and therefore several considerations that are unique to deploying them. | | Enterprise Solution Patterns Using Microsoft .NET (June 2003)
Enterprise Solution Patterns Using Microsoft .NET embraces existing work in the patterns community, contributes new patterns, and shows how to implement these patterns in .NET. The guide explains how a pattern documents simple, proven mechanisms, and shows how collections of patterns provide a common language for developers and architects. The guide then presents a catalog of 32 architecture, design, and implementation patterns that are organized to help you locate the right combination of patterns to solve your problem. | | Guidelines for Application Integration (December 2003)
This guide examines in detail what application integration means and describes the capabilities needed to enable application integration. It discusses the major challenges involved and shows how you can adapt your application integration environment to meet those challenges. It also examines the Microsoft® software products and services you can use to help you design your application integration environment. | | Application Architecture for .NET: Designing Applications and Services (December 2002)
This guide provides architecture-level and design-level guidance for application architects and developers that need to build distributed solutions with the Microsoft® .NET Framework. This guide assumes you are familiar with .NET component development and the basic principles of a layered distributed application design. This guide is most critical to those that architect and design applications or services; recommend appropriate technologies and products for applications or services; make design decisions to meet functional and nonfunctional requirements; or choose appropriate communications mechanisms for applications or services. |
|