ZZZ Projects

ZZZ Projects, founded by Jonathan Magnan, specializes in developer tools like Entity Framework Extensions for EF Core, Dapper Plus, and C# Eval Expression.

[Anton Martyniuk @AntonMartyniuk]

With Dapper you run the application and it crashes because of a bug in SQL string
Here is how to fix it 👇

Dapper is fast and gives you full control over SQL.
But that control comes with a hidden cost.

Every INSERT, UPDATE, and DELETE you write lives inside a string.
And strings have zero type safety.

↳ Rename a column? No compile error.
↳ Change a property type? No compile error.
↳ Misspell a parameter name? No compile error.

You only find out something is broken when your app crashes at runtime.

Here is what most developers do when using Dapper:
❌ Write SQL commands as plain strings
❌ Map every parameter by hand
❌ Repeat the same column lists across Insert, Update, and Delete
❌ Hardcode table and schema names everywhere

One small refactor breaks half of your queries.
And the compiler will not save you.

There is a much better way.

In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗠𝗮𝗽𝗽𝗶𝗻𝗴.

Dapper Plus gives you 3 ways to map your entities to the database - all type-safe.

𝟭. 𝗔𝘂𝘁𝗼 𝗠𝗮𝗽𝗽𝗶𝗻𝗴
→ Zero configuration needed
→ Library matches class name to table name
→ Properties match column names automatically
→ Just call SingleInsert or BulkInsert and it works

𝟮. 𝗗𝗮𝘁𝗮 𝗔𝗻𝗻𝗼𝘁𝗮𝘁𝗶𝗼𝗻𝘀
→ Use [Table], [Column], [Key], [NotMapped] attributes
→ Familiar to anyone using EF Core
→ Keeps mapping next to your model

𝟯. 𝗙𝗹𝘂𝗲𝗻𝘁 𝗔𝗣𝗜 𝗠𝗮𝗽𝗽𝗶𝗻𝗴
→ Full control with strongly-typed lambdas
→ Map only what you need: .Map(x => new { https://t.co/Ihd1gKwJ4f, x.Price })
→ MapAuto method and DapperPlus figures it out for you
→ Refactor-friendly: rename a property and the compiler tells you

You can also organize mappings with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗖𝗼𝗻𝘁𝗲𝘅𝘁:
→ Global context - configure once at startup
→ Instance context - configure per use case
→ Inheritance context - reuse mappings across services

And the best part?

The same mapping works for 𝗯𝗼𝘁𝗵 free Single methods 𝗮𝗻𝗱 paid Bulk methods.

No more SQL strings scattered across your codebase.
No more runtime surprises after a refactor.
Just clean, type-safe writes.

Watch the full video and see all 3 mapping approaches in action.

P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed.

Get started with Dapper Plus Mapping:
https://t.co/DzCnhjbIOo

Here is the source code:
https://t.co/ot8ZPBalcB

How do you solve runtime bugs in SQL strings when using Dapper? Share below 👇

——
♻️ Repost to help others write type-safe Dapper queries

➕ Follow me ( @anton-martyniuk ) to improve your .NET and Architecture Skills

Many thanks to @zzzprojects for sponsoring this post

[ZZZ Projects @zzzprojects]

This article explores the differences between SqlBulkCopy and Dapper Plus, helping developers understand the trade-offs between flexibility, simplicity, and raw speed.

A great read for anyone looking to optimize bulk operations in .NET 👇
https://t.co/sDikwWw6Cu

[Aram Tchekrekjian @AramT87]

@AntonMartyniuk Dapper plus is the best library for bulk operations, super fast and comprehensive. Teams can really benefit from it. Good value for its license. It is an investment for your product.

[Anton Martyniuk @AntonMartyniuk]

📌 Important note:

You can use the following methods for free in Dapper Plus:
→ SingleInsert - insert one entity without writing SQL
→ SingleUpdate - update one entity
→ SingleDelete - delete one entity
→ SingleMerge - upsert in one line (insert or update)
→ SingleSynchronize - keep your data in sync with the source
→ CreateTable - create the table directly from your C# class

Get started with Dapper Plus:
https://t.co/NqbG0pEizp

[Anton Martyniuk @AntonMartyniuk]

Dapper 𝗵𝗮𝘀 𝗮 𝗯𝗶𝗴 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗽𝗲𝗻𝗮𝗹𝘁𝘆 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 insert multiple rows.

Here is how to address this problem 👇

Developers love Dapper for blazing-fast reads.

But for inserting or updating many rows, it becomes painfully slow (even slower than EF Core).

But Why?

Dapper sends each row to the database one by one.
10,000 rows = 10,000 round-trips.

And here is another problem:
↳ You need to write a lot of boilerplate code when using Dapper.

Here is what most developers do when using Dapper:
❌ Write manual INSERT and UPDATE SQL statements
❌ Build complex SQL with hundreds of parameters by hand
❌ Write CREATE TABLE scripts

And the problem is that you don't have type safety when writing SQL commands inside strings. When something goes wrong you will only know at runtime.

There is a much better way.

In my latest video, I show how to solve this with 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀.

👉 𝗦𝘁𝗼𝗽 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 𝗖𝗼𝗺𝗽𝗹𝗲𝘅 𝗦𝗤𝗟 𝘁𝗼 𝗦𝗮𝘃𝗲 𝗗𝗮𝘁𝗮 - 𝗟𝗲𝘁 𝗗𝗮𝗽𝗽𝗲𝗿 𝗣𝗹𝘂𝘀 𝗗𝗼 𝗜𝘁 𝗳𝗼𝗿 𝗬𝗼𝘂.

Dapper Plus gives you clean, simple methods for every write operation.

𝗙𝗿𝗲𝗲 𝗦𝗶𝗻𝗴𝗹𝗲 𝗠𝗲𝘁𝗵𝗼𝗱𝘀:
→ SingleInsert - insert one entity without writing SQL
→ SingleUpdate - update one entity
→ SingleDelete - delete one entity
→ SingleMerge - upsert in one line (insert or update)
→ SingleSynchronize - keep your data in sync with the source
→ CreateTable - create the table directly from your C# class

No more manual SQL.
No more parameter mapping by hand.
Just call the method and Dapper Plus handles the rest.

All single methods are 𝗳𝗿𝗲𝗲 𝘁𝗼 𝘂𝘀𝗲.

𝗣𝗮𝗶𝗱 𝗕𝘂𝗹𝗸 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 (for high performance):
→ BulkInsert
→ BulkUpdate
→ BulkDelete
→ BulkMerge
→ BulkSynchronize

This is where the real magic happens.

I inserted 10,000 product records into the database:
❌ Dapper: 7,000 ms
✅ Dapper Plus BulkInsert: 300 ms

That is over 𝟵𝟲% 𝗳𝗮𝘀𝘁𝗲𝗿 with a single line of code.

Dapper Plus supports SQL Server, PostgreSQL, MySQL, Oracle, MariaDB, and SQLite.

Watch the full video and see every method in action.

P.S.: You can get a free trial for this library and test for 30 days, and you can extend the trial for another month as needed.

Get started with Dapper Plus:
https://t.co/36eO749haH

Here is the source code:
https://t.co/ot8ZPBalcB

How do you currently handle bulk inserts in Dapper? Share below 👇

——
♻️ Repost to help others speed up their Dapper write queries

➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills

Many thanks to @zzzprojects for sponsoring this post

[ZZZ Projects @zzzprojects]

🚀 New video from Anton Martyniuk about improving Dapper performance with Dapper Plus!

If you're working with Dapper and handling large amounts of data, this video is worth watching.
🎥 Watch the video:
https://t.co/rETR5H6dZO

#dotnet #dapper #csharp #sqlserver #programming

[ZZZ Projects @zzzprojects]

🚀 New article by Anton Martyniuk

👉 https://t.co/GGdEkq5til

Returning identity values in EF Core isn’t as simple as it looks.

A quick, insightful read on what happens under the hood and when it really matters 👇

#dotnet #efcore #csharp

[ZZZ Projects @zzzprojects]

🚀 Sharing a great video on Entity Framework Extensions!

If you're working with Entity Framework Core and looking to boost performance, especially for bulk operations, this is definitely worth a watch.

🎥 https://t.co/cKIZPUxn6j

[ZZZ Projects @zzzprojects]

🎬 New video is live!
LINQ Dynamic vs C# Eval Expression: Which One Should You Use?
Anton Martyniuk walks through key concepts and practical examples to help you get up and running.
👉 Watch here: https://t.co/xvHbI7uIBu

[ZZZ Projects @zzzprojects]

New article on YogiHosting!

Learn how to boost your EF Core performance using Entity Framework Extensions for fast bulk operations (insert, update, delete, merge).

👉 https://t.co/pcUBv23BxO

#DotNet #EFCore #EntityFramework #Performance #ZZZProjects

[ZZZ Projects @zzzprojects]

March Monthly Contest Winner
“Definitely the library is amazing, and is ideal for high-performance scenarios where efficiency and clear data access logic matter most.”
— Nelson Solorzano, Freelancer

Thanks for sharing your experience 👏

👉 https://t.co/0xDg5REMRZ

#DotNet #EF

[ZZZ Projects @zzzprojects]

New video in Arabic!

If you're working with Entity Framework, this video is worth checking out.
You’ll learn how to:
✔️ Boost performance

✔️ Reduce execution time

✔️ Handle large datasets more efficiently

Video here: https://t.co/REEgZJUrnF
#dotnet #EntityFramework

[ZZZ Projects @zzzprojects]

📝 New article by Anton Martyniuk

Learn how to get the most out of Entity Framework Extensions by understanding its key options — from column control to performance tuning.

👉 https://t.co/zPRl5qGvH8

[Anton Martyniuk @AntonMartyniuk]

𝗬𝗼𝘂 𝘀𝘁𝗶𝗹𝗹 𝘄𝗿𝗶𝘁𝗲 𝗮 𝗪𝗵𝗲𝗿𝗲 + 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝘀 𝗶𝗻 𝗘𝗙 𝗖𝗼𝗿𝗲?

Please stop! 👇

As you are ruining the performance of your application.

When working with Entity Framework Core, developers often need to retrieve multiple entities from the database based on a collection of IDs or values.

The typical approach is to use the Contains method:

𝚟𝚊𝚛 𝚙𝚛𝚘𝚍𝚞𝚌𝚝𝚜 = 𝚊𝚠𝚊𝚒𝚝 𝚍𝚋𝙲𝚘𝚗𝚝𝚎𝚡𝚝.𝙿𝚛𝚘𝚍𝚞𝚌𝚝𝚜
.𝚆𝚑𝚎𝚛𝚎(𝚙 => 𝚙𝚛𝚘𝚍𝚞𝚌𝚝𝙸𝚍𝚜.𝙲𝚘𝚗𝚝𝚊𝚒𝚗𝚜(𝚙.𝙸𝚍))
.𝚃𝚘𝙻𝚒𝚜𝚝𝙰𝚜𝚢𝚗𝚌();

This approach works fine for small collections, but it creates significant problems when dealing with large datasets:

→ Performance degradation - Even with proper indexes, the SQL WHERE IN clause becomes slower as the number of parameters increases.

→ Parameter limit exceeded - SQL Server has a hard limit of 2,100 parameters per query. While you can work around this by splitting queries into batches in SQL, this is not always practical when using EF Core, especially in complex scenarios with additional filters and joins.

→ Memory and connection issues - Multiple round-trips to the database consume more memory and keep database connections open longer, potentially causing connection pool exhaustion.

This becomes a real problem in scenarios like synchronizing product catalogs, processing bulk orders, or updating inventory across thousands of items.

There is a better solution: 𝗘𝗻𝘁𝗶𝘁𝘆 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻𝘀 library provides specialized methods for bulk data retrieval that solve all these problems.

The library provides specialized methods that use temporary tables internally to bypass the parameter limit and improve performance.

In the video, I show a detailed guide to 5 bulk-read methods using the 𝗘𝗻𝘁𝗶𝘁𝘆 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻𝘀 library.

I explain in depth these methods:
→ WhereBulkContains
→ WhereBulkNotContains
→ BulkRead
→ WhereBulkContainsFilterList
→ WhereBulkNotContainsFilterList

👉 Get the source code of this video:
↳ https://t.co/ux3QAFUCnG

👉 Get started with EF Core Extensions:
↳ https://t.co/NjPzqM4yEz

——

♻️ Repost to help others learn how to perform bulk read operations in EF Core

➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills

Many thanks to @zzzprojects for sponsoring this post.

[ZZZ Projects @zzzprojects]

In this article, you’ll learn how to get started with Entity Framework Extensions and use bulk operations like BulkInsert, BulkUpdate, and BulkMerge to handle large datasets efficiently. https://t.co/9HNgMahA1B

[ZZZ Projects @zzzprojects]

📷 ZZZ Projects — February Newsletter
Stay up to date with the latest updates, releases, and community highlights from the ZZZ Projects team!
https://t.co/lD7KVT3PyC

[ZZZ Projects @zzzprojects]

Want to build a fast and clean CRUD API in https://t.co/1c94knt08a Core?

In this new article from Coding Sonata, you’ll learn how to combine Dapper for lightweight data access with Dapper Plus for high-performance inserts, updates, and bulk operations.

https://t.co/G79wrntOrd

[ZZZ Projects @zzzprojects]

🎥 Sarrawy Dev explains Entity Framework Extensions and how it helps boost performance.
Whether you’re optimizing bulk operations or improving overall efficiency, this video breaks the concepts down in a clear and practical way.

👉 Watch here: https://t.co/VpdJipvMuU

[Anton Martyniuk @AntonMartyniuk]

These options in Entity Framework Extensions library (PART 2)

Will save you hours, days or even weeks of development 👇

Entity Framework Extensions library is not only useful when you need to insert thousands of records.

It also comes with hundreds of useful options that can save a lot of time in your daily routine with EF Core.

In the video, I show a detailed guide on various options with 𝗘𝗻𝘁𝗶𝘁𝘆 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻𝘀 library.

This video is PART 2 in the series.

You can try EF Core Extensions for free with the monthly trial.

👉 Get started with EF Core Extensions:
↳ https://t.co/gv4Eehv5u5

👉 See real-world benchmarks:
↳ https://t.co/JXOKu0A6AY

👉 Get the source code of this video:
↳ https://t.co/nD2NLVS1At

——

♻️ Repost to help others save time with EF Core Extensions

➕ Follow me ( @AntonMartyniuk ) to improve your .NET and Architecture Skills

Many thanks to @zzzprojects for sponsoring this post.

[ZZZ Projects @zzzprojects]

⚡ Working with large data sets in EF Core? This article explains why many developers use Entity Framework Extensions!
https://t.co/4HASaLjpVb

#dotnet #efcore #entityframework #developers #performance #backend #softwaredevelopment