.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Design Pattern for component based development

Posted By:      Posted Date: April 14, 2011    Points: 0   Category :ASP.Net


Requirement : My development is brokene down into Component 1, Component 2 and so on... the output of component 1 goes as input to component 2 and so on...

Questions: Whats the design pattern that might suit my requirement.




View Complete Post

More Related Resource Links

Prototype Design Pattern in C#. Vb.NET

Specify the kind of objects to create using a prototypical instance, and create new objects by copying this prototype

Adapter Design Pattern in C#, VB.NET

Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.

Singleton Design Pattern in C#, Vb.NET

Ensure a class has only one instance and provide a global point of access to it.

Singleton Design Pattern in Asp.net using C#

When we want to make a only one instance of a class and also making sure that there is a global access point to that object then the design pattern we user is called Singleton. The pattern ensures that the class is instantiated only once and that all requests are directed to that one and only object.

The Factory Design Pattern

Software architects generally think in terms of high-level abstractions rather than low-level programming details. Representing a system in terms of high-level abstractions promotes understanding of the system and reduces its perceived complexity. One such set of abstractions is software design patterns. They have been successfully applied in the past to simplify and solve recurring problems in software design.

Abstract Factory Design Pattern (Sample in C# and VB .NET)

An abstract factory provides an interface for creating families of related objects without specifying their concrete classes. Sometimes one wants to construct an instance of one of a suite of classes, deciding between the classes at the time of instantiation. In order to avoid duplicating the decision making everywhere an instance is created, we need a mechanism for creating instances of related classes without necessarily knowing which will be instantiated.

Design Patterns - Using the State Pattern in C#

What is the State Pattern?

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.

Contract-First Web Services: Schema-based Development with Windows Communication Foundation


Schema- first contract-first modeling of Web Services gives you the ability to model your contracts with an XML-centric mindset. This process keeps you focused on universally acceptable types and the hierarchical data structures that can be represented in XML.

Christian Weyer, Buddhike de Silva

MSDN Magazine October 2009

Test-Driven Design: Using Mocks And Tests To Design Role-Based Objects


Use Test-Driven Development with mock objects to design object oriented code in terms of roles and responsibilities, not categorization of objects into class hierarchies.

Isaiah Perumalla

MSDN Magazine June 2009

Patterns: WPF Apps With The Model-View-ViewModel Design Pattern


In this article we explain just how simple it can be to build a WPF application the right way using the MVVM Pattern.

Josh Smith

MSDN Magazine February 2009

Design Patterns: Simplify Distributed System Design Using the Command Pattern, MSMQ, and .NET


Service-oriented architecture is a great framework when you need to perform distributed computing tasks over the Internet. But when you want to perform processing inside your local network, a different solution may provide a better fit. That solution, based on the Command pattern, uses Windows services and Microsoft Message Queuing to implement a queued system that meets your needs better than a service-oriented solution. This article explains how to build it.

Brad King

MSDN Magazine September 2004

Design Pattern

There are various application which are accessing a common web service. Which design pattern can I use?   Application 1 Application 2                   Interface + code              Web service Application 3 

Design Pattern for Checkbox User Dialog C#

Hi Is there a recommended design pattern for a user dialog which has an array of checkboxes? The most rudimentary design seems to be to use an integer as a bitwise paramater which can be passed to and from the dialog based the [checked/unchecked] state of the checkbox(es). Based on approx 3hrs googling the most likely design pattern seems to be "Decorator", but I'm yet to find a C# windows form example. Is "Decorator" the best pattern? Do most people just stick with bitwise manipulation of an integer?  Any examples or url links? Best regards Doug

How Would I Design a Trigger Based on Object Type?

I have doing some research trying to figure out how I could create a trigger or datatemplate that would react based on an Object's type, but haven't found a decent explanation. In code I could use "GetTyoe()" but I am unsure if that is possible in XAML. As a basic example, if the Object is of Type "A" I want to bind the content of a label to a certain property of object "A", but if the object is of Type "B" I want to bind to a different property. I guess the big question is: How do I determine an objects type from XAML?

how to deploy a workflow design in SharePoint Designer 2007 in a list from development server to pro


how to deploy a workflow design in SharePoint Designer 2007 in a list from development server to production server. 

 i create a workflow in a list with SPD 2007 . I want to deploy it to production server who i can do this.

Thanks and Regards Er.Pradipta Nayak

Question of replacement of if..else conditions with design pattern



I am working on an application which contains code in lot of places where certain objects are created based on certain condition. The code is something like the following:

if(affectedObject == "Customer")
     Customer c  = new Customer();
else if(affectedObject == "Salesman")
     SalesMan s = new SalesMan();

// or 

     case "Manager":
          // Do some processing.
     case "Employee":
          // Do another processing.


I have gone through design patterns once but I am not able to figure out how I can use a pattern to replace my code.

Can any one please help me with this? Any practical code sample would be of great help (code without refactoring and refactored code) so that I can understand it better.

Thanks in advance.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend