Some questions can only be answered by organizing your data into groups and then finding groups that contain particular members or have particular properties.
Complex queries can be solved with a combination of simpler LINQ queries, anonymous objects and the Group/By/Into clauses. Using Group/By/Into will also give you the best possible performance for those complex queries.
You don't have to keep all your configuration settings in your config file. There are even some benefits to exporting sections to separate files.
Here's a trick to have Marten automatically deserialize JSON data only when you want it to.
- By Jason Roberts
When you want to find all the objects that are missing a corresponding object, then you need the LINQ equivalent of an outer join. Here, step by painful step, is how to build that query.
You don't need to take your hands off the keyboard to move to another tab in the Toolbox.
If you decide on using an Enum with enumerated values in your Entity Framework class, here are the tools you'll need to make it work. But an enumerated value shouldn't be your first choice.
Here are two ways to save some typing when defining anonymous objects. One only works in Visual Basic, though.
You want to keep an object around only as long as you have memory available, do ya? Then you need the WeakReference class.
Marten is PostgreSQL-based, so take advantage of relational features where it makes sense. Here's an example.
- By Jason Roberts
Peter starts off with a perfectly good solution to a problem but then complicates the problem . . . and ends up moving to a different design pattern. While on that journey he has some best practices around designing Data Transfer Objects.
You probably use ToList to convert your LINQ results into Lists. It's almost as easy to convert any collection into a Dictionary whose items you can retrieve by key.
As a company's problems continue to become more complicated, your code will become more complicated. Peter shows how refactoring code can lead you to better designs.
Peter gets an improved tip from one reader and some more tips from another, all designed to navigate Visual Studio faster.
Sometimes life is like playing Whack-a-Mole: You write some code that solves a problem, and then someone comes along and makes the problem harder. Here's how to continuously integrate new solutions without having to rewrite your old solutions (much).