# linq

Published articles for linq.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Changing Immutable Collections

DevFeed: [Changing Immutable Collections](<https://devfeed.tech/articles/changing-immutable-collections-30704.md>)

Original publisher: [Read original article](<https://codeblog.jonskeet.uk/2025/12/31/changing-immutable-collections/>)

Author: jonskeet

Published: 2025-12-31T10:32:45Z

Content type: article

Language: en

Sources: [Jon Skeet](<https://devfeed.tech/sources/jon-skeet.md>)

Topics: [C#](<https://devfeed.tech/topics/csharp.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [array](<https://devfeed.tech/tags/array.md>), [arrays](<https://devfeed.tech/tags/arrays.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [collection](<https://devfeed.tech/tags/collection.md>), [election-2029](<https://devfeed.tech/tags/election-2029.md>), [immutability](<https://devfeed.tech/tags/immutability.md>), [linq](<https://devfeed.tech/tags/linq.md>), [migration](<https://devfeed.tech/tags/migration.md>), [properties](<https://devfeed.tech/tags/properties.md>)

### AI overview

The article explains a migration from ImmutableList<T> and ImmutableDictionary<TKey, TValue> to immutable collection types better suited to code that creates collections and then leaves them unchanged. It describes the migration steps and related helper-method and property-type changes.

### Source excerpt

As I've written before, I'm leaning heavily into immutability in the election site code. Until September 2025 (it's taken a long time to get round to writing this blog post) that meant a combination of records, ImmutableList<T> and ImmutableDictionary<TKey, TValue>. In an ECMA C# standards meeting, however, Joseph Musser passed on some really valuable feedback ... Continue reading Changing Immutable Collections ->

## Using LINQ to Query MongoDB in a .NET Core Application

DevFeed: [Using LINQ to Query MongoDB in a .NET Core Application](<https://devfeed.tech/articles/using-linq-to-query-mongodb-in-a-net-core-application-21814.md>)

Original publisher: [Read original article](<https://www.thepolyglotdeveloper.com/blog/2022/04/using-linq-query-mongodb-dotnet-core-application/>)

Author: Nic Raboy

Published: 2022-04-06T13:00:00Z

Content type: tutorial

Language: en

Sources: [Nic Raboy](<https://devfeed.tech/sources/nic-raboy.md>)

Topics: [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [net core](<https://devfeed.tech/topics/net-core.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [csharp](<https://devfeed.tech/tags/csharp.md>), [dotnet](<https://devfeed.tech/tags/dotnet.md>), [linq](<https://devfeed.tech/tags/linq.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [net-core](<https://devfeed.tech/tags/net-core.md>), [nosql](<https://devfeed.tech/tags/nosql.md>), [programming](<https://devfeed.tech/tags/programming.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>)

### AI overview

This tutorial demonstrates how to use LINQ in a .NET Core console application to query MongoDB documents. It covers replacing simple MongoDB queries and aggregation pipelines with C# LINQ syntax, using MongoDB Atlas, configuring the project, and selecting LINQ Version 3.

### Source excerpt

If you've been keeping up with my series of tutorials around .NET Core and MongoDB, you'll likely remember that we explored using the Find operator to query for documents as well as an aggregation pip... The post Using LINQ to Query MongoDB in a .NET Core Application appeared first on MongoDB.

## Ruby and .NET: Comparing Language Features and Developer Communities

DevFeed: [Ruby and .NET: Comparing Language Features and Developer Communities](<https://devfeed.tech/articles/parenthetical-thesis-on-ruby-net-or-irongem-or-whatever-the-kids-call-it-these-days-33376.md>)

Original publisher: [Read original article](<https://timkellogg.me/blog/2011/08/29/parenthetical-thesis-on-rubynet-or>)

Published: 2011-08-29T00:00:00Z

Content type: opinion

Language: en

Sources: [Tim Kellogg](<https://devfeed.tech/sources/tim-kellogg.md>)

Topics: [Ruby](<https://devfeed.tech/topics/ruby.md>), [.NET](<https://devfeed.tech/topics/net.md>), [C#](<https://devfeed.tech/topics/csharp.md>), [F#](<https://devfeed.tech/topics/fsharp.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [expression](<https://devfeed.tech/tags/expression.md>), [extension](<https://devfeed.tech/tags/extension.md>), [f-sharp](<https://devfeed.tech/tags/f-sharp.md>), [linq](<https://devfeed.tech/tags/linq.md>), [mixins](<https://devfeed.tech/tags/mixins.md>), [monkey-patching](<https://devfeed.tech/tags/monkey-patching.md>), [net](<https://devfeed.tech/tags/net.md>), [python](<https://devfeed.tech/tags/python.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>)

### AI overview

The author compares Ruby and .NET, highlighting Ruby's mixins, monkey patching, REPL, and blocks alongside C#'s type safety, LINQ, and expression trees. The author concludes that neither platform is inherently better, but prefers the Ruby community.

### Source excerpt

Since college I've always been a huge fan of dynamic languages. I was really into Python for a long time and in the past year or so I've picked up Ruby. It's well known that the open source/dynamic language world has always looked down on the .NET/Java world as some sort of inferior. While having a conversation with a colleague about ruby versus .NET I stumbled on a conclusion.Ruby has some great features like mixins, monkey patching, a REPL. I also love how blocks make closures such an accessible and natural way to program. Ruby makes easy things easy and hard things fun.On the other hand, C# is one of the most beautiful typesafe languages (although F# is gaining favor with me). Linq and expression trees provide functionality that you literally cannot reproduce in dynamic languages (it requires knowledge of types, which dynamic languages theoretically shouldn't care about). With the crazy stuff that people are doing with expression trees (building SQL statements, mapping objects, selecting properties, etc) it makes it hard to say I'd rather be doing ruby.While C# has some analogous ruby constructs (extension methods are kind of like a lesser form of monkey patching), it still suffers from some of the classical faults of static languages (there can be a lot of extra code just to deal with types and to play nicely with the compiler). At the same time, the compiler also writes tests for you (a contract states you will have these methods, yet in ruby you can't ever be completely sure they'll actually be there. Something that you'd have to write unit tests for in ruby).The conclusion I came to was that, at this point in time, there really isn't a compelling reason why ruby is better than .NET or vice versa. Except for one thing - the communities. The ruby community is nearly too much fun. In Boulder, where I live, there are several companies that host regular hackfests. There are also annual ruby conventions where people get together, socialize, and share new ideas. In