Design Patterns – Which to use When? Take the Quiz!(dotnetcube.com)

submitted by dncdude(1350) 2 years, 7 months ago

I received several questions on how to pick a Design Pattern, which motivated me to write this post. As it was mentioned in the Design Patterns overview article, there is no rule of thumb in selecting a Design Pattern. Developers should not choose a design pattern and design a solution around it. Instead they need to analyze at a higher level, the problem they are attempting to solve and pick a Design Pattern that is most appropriate. read more...

add a comment |category: Architecture |Views: 704

tags: Architecture another

Design Patterns – Using the State Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 7 months ago

The State Pattern is a behavioral pattern that can be used to alter the behavior of an object at run time. As the state of an object changes, the functionality of the object can change drastically. This change of behavior is hidden from the Client and the Client interfaces with a wrapper object known as the Context. The State Pattern is a dynamic version of the Strategy Pattern. read more...

add a comment |category: Architecture |Views: 397

tags: Architecture another

Design Patterns – Using the Chain of Responsibility Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 7 months ago

The Chain of Responsibility Pattern is a behavioral pattern that works with several handlers that has limitations on what requests they could handle. If the handler cannot process a request, it passes on the request to a successor handler. At the end of this chain of handlers, there can either be default or exceptional behavior. This pattern is encountered very frequently in real life. Consider a computer retailer that provides tech support to it’s customers. When a customer calls with a simple problem, it’s usually handled by Level 1 Support. For a serious computer issue such as a broken system, the Level 1 support cannot handle this issue and usually pass this on to a higher level of support or a manager. read more...

add a comment |category: Architecture |Views: 351

tags: Architecture another

Design Patterns – Using the Observer Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 8 months ago

The Observer Pattern belongs to the category of Behavioral patterns. In some applications, the state of an object (the subject) is constantly changing (Ex: the price of a product varies depending on market demand). There could be other objects (observers) that are interested in getting notified when the state of the subject changes. The Observer Pattern can be used to communicate the changes between a subject and one or more observers. The Observer Pattern defines a one to one dependency between the subject and the observers so that when a subject changes state, all the observers are notified. read more...

add a comment |category: Architecture |Views: 332

tags: Architecture another

Design Patterns – Using the Builder Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 8 months ago

The Builder Pattern falls under the category of the Creational Patterns as it controls the instantiation of a class. This pattern is suitable in scenarios in which an object is made up several parts and the constituent parts need to be created in the same order using an algorithm. A real world example is in making a pizza. A pizza is made up of several parts (the crust, cheese and the toppings) that are constructed using an algorithm (bake the crust, add cheese and add the toppings). read more...

add a comment |category: C# |Views: 410

tags: C# another

Design Patterns – Using the Abstract Factory Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 8 months ago

The Abstract Factory Pattern provides an interface for creating families of related objects without specifying their concrete classes. The Abstract Pattern makes sure that the client does not know anything about the objects being created. The pattern hides the implementation of the product definitions and their class names and the only way the client can create a product is through the factory. read more...

add a comment |category: Architecture |Views: 452

tags: Architecture another

Design Patterns – Using the Decorator Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 9 months ago

Decorator Patterns belong to the Structural Pattern category and it’s role is in providing a way of attaching new behavior to the object at run time. The object is unaware of the new behavior and this pattern is a good candidate for enhancing legacy applications. Decorator Pattern provides a way of adding functionality to an existing class without using inheritance. read more...

2 comments |category: Architecture |Views: 613

tags: Architecture another

Design Patterns – Using the Composite Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 9 months ago

Composite Pattern enables a client to treat a single entity and a collection of entities in the same way. Frequently, developers create systems in which a component may be an object or a collection of objects. For example, an application that gathers metrics on the size of the files/folders in a file system would like to treat the folder and the file in the same way. A folder is either empty or composed of one or more files. The size of a folder is the size of the individual files that make the folder and the size of the file is the size of that individual file itself. The Composite Pattern is designed to accommodate such a requirement. read more...

add a comment |category: C# |Views: 381

tags: C# another

Design Patterns – Using the Adapter Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 9 months ago

An Adapter pattern also known as the “Wrapper pattern” makes it easier to implement solutions that interface with multiple systems. There are situations in which a system we are working needs to interact with another system, third party API or a legacy component. This interaction becomes challenging if the systems are not compatible with each other. There is no standard way to implement a particular system. How do we make it easy to tie all the incompatible systems together? With the help of the Adapter pattern. read more...

add a comment |category: C# |Views: 544

tags: C# another

Design Patterns – Using the Singleton Pattern in C#(dotnetcube.com)

submitted by dncdude(1350) 2 years, 10 months ago

Singleton Pattern belongs to the category of Creational Patterns. If you recall from the Overview article, the Creational Patterns are the subset of Design Patterns that encapsulate the logic of object creation. In a Singleton Pattern, there is a class (Singleton class) that ensures that only a single instance of itself can be created. It also provides a global point of access to this instance. So, irrespective of where in your code base this class is instantiated, you will always get access to the same instance. read more...

add a comment |category: C# |Views: 468

tags: C# another

Design Patterns – Using the Strategy Pattern in C(dotnetcube.com)

submitted by dncdude(1350) 2 years, 10 months ago

A Strategy Pattern belongs to the Behavioral Pattern category. It helps in de-coupling the client and the algorithms into separate classes. The object and it’s behavior are encapsulated into their own classes. This pattern helps in several ways. It helps you to switch algorithms at any time. In future, if you decide to add a new algorithm, it’s simpler as all you have to do is add a new class that encapsulates the new behavior. read more...

add a comment |category: C# |Views: 21

tags: C# another

Design Patterns – An Overview(dotnetcube.com)

submitted by dncdude(1350) 2 years, 11 months ago

Design patterns are language independent mechanisms for providing solutions to common problems. Adhering to design patterns help in creating systems that are robust, scalable and maintainable as design patterns follow best practices and established standards. Design patterns have existed in non software engineering disciplines for a long time. Mechanical engineers reuse proven standard design models when designing a new kind of lathe machine. Instead, they reuse existing designs. read more...

add a comment |category: C# |Views: 19

tags: C# another

C# 3.0 - Extension Methods(dotnetcube.com)

submitted by dncdude(1350) 2 years, 11 months ago

Extension methods let developers add methods to an existing type without having to recompile. Extension methods are static methods that can be used as instance methods of the type that was extended. read more...

add a comment |category: C# |Views: 10

tags: C# another

Useful Visual Studio Shortcuts-Some new VS 2010 shortcuts included too(dotnetcube.com)

submitted by dncdude(1350) 2 years, 11 months ago

Here’s a compilation of some Visual Studio keyboard shortcuts that I personally find useful. I have included some that may make their way into the Visual Studio 2010 release. read more...

1 comment |category: ASP.NET |Views: 617

tags: ASP.NET another

Overview of .NET 4.0 features – C# 4.0 Named and Optional Parameters(dotnetcube.com)

submitted by dncdude(1350) 2 years, 11 months ago

The concept of Optional parameters is not new and exists in other languages such as C++. Infact, the functionality is a part of the .NET framework and exists is in VB.NET. Optional parameters will be introduced in C# 4.0 and can be used to call a method without having to specify all the arguments. The intent of this feature is to assist in writing concise code and in COM interoperability. read more...

1 comment |category: C# |Views: 436

tags: C# another

Overview of .NET 4.0 features – ASP.NET 4.0 ClientIDMode(dotnetcube.com)

submitted by dncdude(1350) 3 years ago

In pre 4.0 days, when a server control is rendered, the framework would assign an ID to the control based on the control hierarchy. For example, a textbox of id "txtTest" in a user control that is used on a page would be rendered with the ID "WebUserControl11_txtTest". Developers could use the ClientID property (ex: txtTest.ClientID) in the code behind to retrieve the ID assigned to the control by the framework. It was essential for the framework to assign the IDs this way to maintain uniqueness of the IDs on a page. In the prior example, the User Control that inherits from the System.Web.UI.UserControl implements the INamingContainer interface. Any control (either custom or a .NET control) that implements this interface would ensure unique naming scope for the child controls. read more...

2 comments |category: ASP.NET |Views: 612

tags: ASP.NET another