Course info
Oct 8, 2010
1h 23m

This course looks at using LINQ in the business and data access layers of an application. We'll describe how to use LINQ features to create more expressive business logic by applying functional programming and building fluent APIs. We'll also see the impact of LINQ on build data access components and discuss the tradeoffs of laziness versus greediness.

About the author
About the author

Scott has over 15 years of experience in commercial software development and is a frequent speaker at national conferences, and local user groups. Scott is a Microsoft MVP and has authored books on several Microsoft technologies, including ASP.NET, C#, and Windows Workflow.

More from the author
ASP.NET Core Fundamentals
5h 44m
Jan 23, 2019
More courses by Scott Allen
Section Introduction Transcripts
Section Introduction Transcripts

LINQ - Beyond Queries
Hi. This is Scott Allen of Pluralsight, and in this module we're going to look at using LINQ to do more than just query data. We're going to see how the features added into the C# language for language integrated query can allow you to write better business logic. We'll be looking at features like extension methods, expression of T and expression trees, and the funcs and action types that are now in the. NET framework. These were all features that were added to the framework into the C# language ostensibly to facilitate LINQ and enable Microsoft to build LINQ features, but what we found is that these features are generally useful outside of a LINQ context. for instance, we can use extension methods to build better APIs and fluent APIs. We can use expression trees to perform what's known as static reflection, and we'll see how we can use function actions to apply a functional declarative programming style to our applications that in some scenario is going to be easier to read than the imperative style. Along the way I'll do some demonstrations of using a functional programming approach to validation; these validations will become more and more complex as we move along, so we'll eventually see how we could build a LINQ-powered rules engine.