We introduce you to the benefits of building composite applications with the Composite Application Guidance for WPF from Microsoft patterns & practices.
MSDN Magazine September 2008
View Complete Post
This article discusses the Project Linker tool and other techniques to create applications that target both WPF and Silverlight from a single code base.
Erwin van der Valk
MSDN Magazine August 2009
This article reviews the Prism project developed by the Microsoft patterns & practices group and demonstrates how to apply it to composite Web applications using Silverlight.
MSDN Magazine July 2009
Danny Simmons explores some anti-patterns you should look out for when building n-tier applications with the Entity Framework.
MSDN Magazine June 2009
We show you how .NET Services within the Azure Services Platform makes it easy to bring workflow apps to the cloud.
MSDN Magazine April 2009
Integrated Desktop is a loosely coupled hosting architecture and composite UI that runs on the desktop and is supported by a loosely coupled architecture on the back end. It collapses the number of applications a user must deal with when making decisions.
Christian Thilmany and Jim Keane
MSDN Magazine September 2006
In this article the authors provide an in-depth examination of the architecture of SharePoint products and technologies: WSS and SPS. WSS provides the foundation for creating collaborative Web sites that support customization and personalization and SPS complements WSS by playing the role of a content aggregator. This article explains how.
Jason Masterman and Ted Pattison
MSDN Magazine July 2004
Part 1 of this series discussed how types built for the common language runtime can be shared among applications in the Microsoft .NET Framework regardless of the .NET languages used to build them. This second part continues with building assemblies by first covering security, sharing assemblies, versioning, localization, and side-by-side execution. Because in .NET two DLLs with the same name can be loaded as long as another attribute-which can include the localization language-differs, versioning is much easier than it used to be, so DLL Hell may become a thing of the past.
MSDN Magazine March 2001
Types that are built for the Common Language Runtime can be shared among applications in the Microsoft .NET Framework no matter which of the .NET languages they were built in, an obvious benefit to developers. This article describes the building, packaging, and deploying of applications and types for the .NET Framework, including the role and significance of assemblies, private and otherwise. The way metadata and assemblies help to solve some historical problems like versioning conflicts and DLL Hell, and how they improve system stability are also discussed.
MSDN Magazine February 2001