Last post Aug 29, 2017 07:33 AM by XIII
Aug 29, 2017 05:54 AM|nideeshm|LINK
What is the design pattern behind linq Query.
Student a = dbContext.Students().where().select().first()
output of students() is a Iqueryable, which is passed as input to Where(), whose ouput is again Iquerable, again passed as input to Select(), whose ouput is passed as input to first.
I need a similar functionality, where there would be multiple actions/methods, and actions/methods can be given in any order.
I checked out Chain of responsibility. But i do not want to set successor for each time I create a handler object.
Aug 29, 2017 07:33 AM|XIII|LINK
I think you're after method chaining. For example: