Anonymous types are useful, especially in LINQ queries where you often want to iterate through an array of items and project them into some arbitrarily shaped objects that are little more than simple data containers, using anonymous types save you the hassle of having to first declare those types which you will simply throw away afterwards.
One thing you can’t easily do with anonymous types however, is to return them from the method it’s declared in and use them elsewhere. Sure, you can return an instance of an anonymous type as object, but that doesn’t make it any easier to work with them as you don’t have access to any of the properties on the anonymous type. So what can you do in those cases?
Cast By Example
This is a nifty technique which can deals with the above problem, and all you need is a simple method like this:
You can then take an instance of an anonymous type and cast it back to its original shape:
This works, but only if the example is the exact shape as the original, otherwise you’ll get an InvalidCastException:
An alternative to using the Cast By Example technique is to take advantage of the dynamic keyword introduced in C# 4, whilst this approach makes everything soooo easy, the trade off is that you lose intellisense support.
Of course, if you try to use a property that isn’t defined on the anonymous type then you’ll get an exception at runtime, specifically the RuntimeBinderException.
Both techniques can help make life easier if on the rare occasion you need to return an anonymous type from your method, but if you find yourself doing that frequently in your code then it’s probably best to take a step back and rethink your overall architecture. Anonymous types are confined to methods by design, and for a good reason! If you’ve structured your code correctly following good OOP design principles then there should be very little need to ‘hack’ your way through using these techniques! So as a parting shot, please use these techniques with caution and only when absolutely necessary!
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong