What is the difference between Architecture and Design patterns ? Can anyone please classify them. ?
I m so confused. Don't think as a stupid question
View Complete Post
Sten Sundblad and Per Sundblad
MSDN Magazine July 2003
A design pattern can solve many problems by providing a framework for building an application. Design patterns, which make the design process cleaner and more efficient, are especially well-suited for use in C# development because it is an object-oriented language. Existing design patterns make good templates for your objects, allowing you to build software faster. This article describes several popular design patterns you can use in your own applications, including the singleton, the decorator, the composite, and the state classes, which can improve the extensibility of your applications and the reuse of your objects.
MSDN Magazine July 2001
I need help to make decision for making framework for new project.Project is financing (banking) project. It'll b using .net 3.5 sp1 with sql server 2005.I want to know what should be best approach for framework? Mean to use LINQ or go with Stored procedure way with 3 tier architecture?or anything else?
For current financing project the framework is done by one of MVP. He used LINQ to all things.But we facing problem of w3wp process hang. We cant go for web gardening or farming bcz LINQ objects cnt be serialized to store in Session etc.Difficult to use Transactions in LINQ. Have to use TransactionScope lead to MSDTC problems etc.
Please give your opinion.
The Model-View-ViewModel (MVVM) design pattern describes a popular approach for building Windows Presentation Foundation or Microsoft Silverlight applications. Robert McCarter shows you how the ViewModel works, and discuss some benefits and issues involved in implementing a ViewModel in your code.
MSDN Magazine July 2010
The end goal of software projects is to deliver value to the customer. Software design is a major factor in how successfully a team can deliver that value. The best designs are a product of continuous design rather than the result of an effort that tries to get the entire design right up front. This approach lets you strive to apply lessons learned from the project to continuously improve the design, instead of becoming locked into an erroneous design developed too early in the project.
MSDN Magazine August 2009
Design patterns provide a common, repeatable approach to solving software development tasks, and many different patterns can describe how to accomplish a certain goal in code. When developers begin working with Windows Workflow Foundation (WF), they often ask about how to accomplish common tasks with the technology. This month's column discusses several design patterns used in WF.
Now that you're even managing projects in the cloud, you'll need some tools to help. This month we illustrate one, discuss UX design patterns, a book by Anders Hejlsberg, and more.
MSDN Magazine June 2009
In this article we explain just how simple it can be to build a WPF application the right way using the MVVM Pattern.
MSDN Magazine February 2009
Designing testability into your app means smaller tests that are cheaper to create, easier to understand, faster to run, and much simpler to debug.
MSDN Magazine December 2008
The MVP pattern helps you separate your logic and keep your UI layer free of clutter. This month learn how.
MSDN Magazine August 2006
Today there is a greater focus than ever on reusing existing components and wiring together disparate components to form a cohesive architecture. But this wiring can quickly become a daunting task because as application size and complexity increase, so do dependencies.
MSDN Magazine September 2005