Articles filed in category 'Patterns'

In an application built with object-oriented techniques, objects are the bricks.You construct little pieces of code encapsulated in these bricks. To build bigger structures, you need to hold these bricks together. You can hardwire them together by instantiating dependent objects within your objects, but it makes the whole structure less flexible in the face of change. So you can adopt an inversion of control (IoC) container to act as your mason to assemble your bricks in...to complex structures that can flex with changing requirements. In this article, I will examine a popular IoC container, Castle Windsor, and how it enables you to build flexible and robust applications. If you are new to IoC containers and dependency injection, I would recommend reading Martin Fowler's article, Inversion of Control Containers and the Dependency Injection Pattern (http://martinfowler.com/articles/injection.html) and my own article from the March 2008 edition of MSDN Magazine, Loosen Up: Tame Your Dependencies for More Flexible Apps (http://msdn.microsoft.com/en-us/magazine/cc337885.aspx).See More

The ASP.NET Provider Model drives many features within the ASP.NET architecture, yet most people only relate it to security or membership-related functionality. In this article, I’ll take you deep into the provider model, show you how it’s used from a security context, then take it up a notch and teach you how you can use it to turn any feature in your application into an extensible and swappable component. In fact, I’ll even show you why calling it the ‘ASP.NET’ Provide...r Model may be a misnomer.The ASP.NET Provider Model drives many features within the ASP.NET architecture, yet most people only relate it to security or membership-related functionality. In this article, I’ll take you deep into the provider model, show you how it’s used from a security context, then take it up a notch and teach you how you can use it to turn any feature in your application into an extensible and swappable component. In fact, I’ll even show you why calling it the ‘ASP.NET’ Provider Model may be a misnomer.See More

Do more with less code is the slogan of Visual Studio 2005.When it comes to reducing the amount of written code, wizards are definitely a viable option. Visual Studio 2005 has a lot of wizardry in it, especially to generate data access code. Any code that gets silently injected in your project follows a strict logic and a well-known design pattern. A full understanding how Visual Studio 2005 does it puts you on the right track to modify and extend the code to build your ...made-to-measure data access layer. This article dissects the code behind table adapters and binding source components to unveil patterns and best practices.See More

Nov/Dec 08 .NET Rocks by Carl Franklin

As developers are just getting used to ASP.NET MVC 2 and Visual Studio 2010, Microsoft has already planned and released a preview of the next version of ASP.NET. What started out as “just another option” for ASP.NET developers has become the programming style of choice for developers writing .NET applications for the web.

Ben Coe gives us tips on planning an engineering project when you’re starting with a blank slate. He starts with hosting options, addresses scaling, and looks at tools like Heroku, Amazon’s Web Services (AWS), Amazon’s Elastic Computing Cloud (EC2), and the Twelve-Factor App Manifesto.

Martin introduces Design by Contract and Code Contracts, and gives you a sneak preview of Pex—Microsoft’s new test-suite generator. Along the way, he will show you how to add contracts to ADO.NET entities and some interesting coding strategies, good practices, and pitfalls you may encounter while making a deal with your code.With Code Contracts, Microsoft delivers its own flavor of Design by Contract for the .NET Framework. But wait, what is this thing sometimes called C...ontract-First Development? How will it change the way you develop software and write your unit tests? And first and foremost, how do you use Code Contracts efficiently?In this article, I will introduce Design by Contract and Code Contracts, as well as give you a sneak preview of Pex-Microsoft’s new test-suite generator. Along the way, I will show you how to add contracts to ADO.NET entities and some interesting coding strategies, good practices, and pitfalls you may encounter while making a deal with your code.See More

Building loosely coupled application architectures requires more than just separating your application into different layers.In this article, I’ll take a project that was built using techniques that result in fragile, hard-to-test code and introduce some principles, techniques, and refactorings that will help you realize flexibility and testability in your applications.

Struggling to grasp the concepts of Model-View-View-Model? Keep it simple!

Jimmy explores what went right and what went wrong with version 1.0 of AutoMapper.

Ned introduces the most significant advance in error handling since exceptions and he shows you a new way to look at errors.This article introduces the most significant advance in error handling since exceptions.You get improved tools for today and a glimpse of radical possibilities for tomorrow. You get a framework which supports more expressive error handlers and gives them equal access to error context information. You get a roadmap for adding improved error handling ...capabilities, including class-level error handlers and the ability to fix errors at run time. Above all, you get a new way to look at errors.See More

Derick outlines how to achieve the benefits of low coupling, high cohesion, and strong encapsulation. He also shows how the five S.O.L.I.D. design principles can get you there.Most professional software developers understand the academic definitions of coupling, cohesion, and encapsulation.However, many developers do not understand how to achieve the benefits of low coupling, high cohesion and strong encapsulation, as outlined in this article. Fortunately, others have cr...eated stepping stones that lead to these goals, resulting in software that is easier to read, easier to understand and easier to change. In this article series, I will define three of the primary object-oriented principles and show how to reach them through the five S.O.L.I.D. design principles.See More

In this article, Miguel Castro elucidates the evolution of multithreading in .NET, emphasizing the transition toward parallel programming through the Task Parallel Library (TPL) and the use of `async` and `await` keywords. He clarifies misconceptions about concurrency versus true multithreading, highlights the benefits of TPL’s `Task` and `Parallel` classes for manageable and efficient asynchronous code, and demonstrates how the modern async/await syntax simplifies non-b...locking operations, especially critical in responsive mobile apps. Castro encourages developers to embrace these tools to write clear, scalable, and user-friendly parallel code without the complexity of traditional threading.See More

John Baird surveys Windows Phone 7 development through the lens of MVVM, Silverlight, and unit testing, arguing that WP7’s constrained hardware and integrated Silverlight/XNA stack make clean architecture essential. He demonstrates how data binding, data templates, and declarative layouts simplify UI development, reduces boilerplate, and enables testable code. The article outlines MVVM concepts (Model, View, ViewModel), explains how to construct a testable base and comma...nds, and shows how to scaffold an MVVM project with Models, Views, and ViewModels for a sample expense-tracking app.See More