Use a delegate when: 1. An eventing design pattern is used. 2. It is desirable to encapsulate a static method. 3. The caller has no need access other properties, methods, or interfaces on the object implementing the method. 4. Easy composition is desired. 5. A class may need more than one implementation of the method and it will be decided at runtime as to which method to call. Delegates are also used when call back functionality is to be implemented : Refer http://www.knowdotnet.com/articles/delegatesreplaceraiseevents.html[^] Hope this helps. All the best.

Start off by working out what you actually want your project to do, and how you want it to work. Once you know that, you need to break the application down into smaller areas and start thinking about how to compartmentalize the different aspects of the app. Don't get hung up on designing for patterns; let it come naturally. I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be Forgive your enemies - it messes with their heads My blog | My articles | MoXAML PowerToys | Onyx

ok thanks for the links. one more doubts, how to handle click events below submit button in the .ashx page. context.Response.Write( "");

Kindly avoid posting this kinda post in Programming forum. Might be you can try Lounge or so.

You don't know about www.google.com

You can not access a Div without add runar="server" in code behind. But you can get input element without add runar="server" like this: in code behind string pName = Request.Form['pName'];

Generally its the same here. Some employers might be different but the majority coming out of uni can't program. For the few programming modules there are, lecturers tend to give out the full code solution anyway so people just copy without understanding it.