# Type Analysis Conflict: "dynamic" type becomes unusable in Dapper/EF after installing v1.21.1 on .NET 8 **URL:** \ **Category:** bug?\ **Tags:** sql-server, aspnetcore\ **Created:** [May 8, 2026, 8:57am UTC](https://discuss.hangfire.io/t/type-analysis-conflict-dynamic-type-becomes-unusable-in-dapper-ef-after-installing-v1-21-1-on-net-8/11426 "2026-05-08T08:57:37Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Hossam.DevOps](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@Hossam.DevOps](https://discuss.hangfire.io/u/Hossam.DevOps)\ **Post date:** [May 8, 2026, 8:57am UTC](https://discuss.hangfire.io/t/type-analysis-conflict-dynamic-type-becomes-unusable-in-dapper-ef-after-installing-v1-21-1-on-net-8/11426/1 "2026-05-08T08:57:37Z")
Hello, I am the Lead Backend Engineer for a fintech/multi-vendor platform ( **Maqadhi** ). We recently encountered a strange behavior when upgrading `Hangfire.PostgreSql` to version **1.21.1** in a **.NET 8.0** environment. **The Issue:** After installing v1.21.1, the IDE (Visual Studio/Rider) and the compiler started throwing errors on unrelated Dapper queries that use the `dynamic` type. The error was: `"Type 'dynamic' has no settable fields or properties"`. **Findings:** - The code was working perfectly on SQL Server and on older versions of the PG storage. - Removing v1.21.1 or downgrading to **v1.20.9** immediately resolves the issue. - This suggests a dependency conflict (possibly with `Npgsql` or metadata resolution) that affects the Dynamic Language Runtime (DLR) interpretation in .NET 8. **Environment:** - Target Framework: .NET 8.0 - Dapper Version: 2.1.66 - Hangfire.PostgreSql: 1.21.1 (Broken) vs 1.20.9 (Working) ![d3843f34-2d3d-458c-ac93-5291ca7aaf79](https://europe1.discourse-cdn.com/flex017/uploads/hangfire/original/2X/8/85d22894666784948c4808e7fc81ad0775a64ca4.png) Has anyone else experienced this metadata/DLR pollution with the latest version?