Unlock the power of .NET’s latest collection types!

by Jul 9, 2024

Unlock the power of .NET’s latest collection types!

Here’s a guide for when to best use the new Readonly, Immutable, and Frozen collections. You won’t believe how it can optimize your code! 👇

1️⃣ Readonly

Readonly is a readonly view of the original collection it was created from.

Useful to return to callers to indicate it is only for readonly use.

Keep in mind: It is still possible to update the underlying original collection.

2️⃣ Immutable

Immutable collection really can’t be changed after creation.

But it still has methods Add(), Remove() and Replace()? You can change the collection, but every change will return a new Immutable collection! It does internal linking to make sure it is still memory optimized.

Immutable is perfect for thread-safe modifications. Modifications are amazingly fast. No need for the slower Concurrency collections.

3️⃣ Frozen

Frozen collections are also readonly, but optimized like crazy for read access.

How? When you create a Frozen collection, it will find the best algorithm and structure to represent your data for read-heavy scenarios. Downside: it will cost more time to create the collection.

Frozen is a good fit, when you create it once (for example at the start of your app) and use it many times to lookup stuff.

Are any of these new collections useful for you?

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Microsoft Teams: Too Many Apps in One?

Microsoft Teams: Too Many Apps in One? All-in-one apps like Teams? That’s a hard pass from me. Microsoft Teams wants to be the one app to rule them all. But I’m the guy who likes my apps separate, like LEGO bricks—not superglued together. I open my To-Do app...

read more

I see your comment. And I see AI fingerprints all over it.

I see your comment. And I see AI fingerprints all over it. You know the ones where you think: Bro... did you even read my post? 😅 I get it. We want engagement. We want the algorithm to give us more eyeballs. But fake engagement is still fake. Here’s what happens when...

read more

Abstract the abstraction 🤯.

Abstract the abstraction 🤯. .NET devs, we love our patterns... maybe too much. For a simple CRUD app, I've seen: Repositories – because obviously we can't query directly, that's too mainstream UnitOfWork – like transactions, but now with extra ceremony Services –...

read more