How do I install the Fix Dependency Model skill?

Run npx skillmds@latest add pavelt-papaya/fix-dependency-model in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fix Dependency Model safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fix Dependency Model?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fix Dependency Model free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fix Dependency Model?

pavelt-papaya (@pavelt-papaya) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fix Dependency Model by pavelt-papaya

Name: Fix Dependency Model
Author: pavelt-papaya

Fix Dependency Model

Fixes AWS deploy crash "Could not load file or assembly 'Microsoft.Extensions.DependencyModel'" in Shine/Playon .NET services. Root cause is Dockerfile `dotnet publish` of the whole solution into one flat out/ folder — test projects (coverlet.collector) overwrite the host's DependencyModel. Fix by setting IsPublishable false on test projects. Use immediately when this exception, assembly-not-found for DependencyModel, or a coverlet/test-publish version clash appears. Do not add a Host PackageReference for DependencyModel.

pavelt-papaya Updated Sep 22, 2026

File contents

Fix Microsoft.Extensions.DependencyModel publish clash

Error

Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly
'Microsoft.Extensions.DependencyModel, Version=10.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'

Serilog raises this while reading its configuration. It is a race: last writer to out/ wins, so it only shows up after test-project or publish-order changes.

Root cause

The Dockerfile runs dotnet publish on the whole solution into a single flat out/ folder that becomes the runtime image.

The solution includes test projects. coverlet.collector ships Microsoft.Extensions.DependencyModel 8.0.2; the Host needs 10.x. Both write the same filename. When coverlet's copy wins, the host asks the CLR for assembly version 10.0.0.0 and gets 8.0.0.0.

Do not pin or add Microsoft.Extensions.DependencyModel on the Host csproj / Directory.Packages.props. That papers over the clash; the next test dependency can still overwrite out/.

Fix

Find every test project (*Tests*.csproj, *Test*.csproj).
Add <IsPublishable>false</IsPublishable> beside the existing <IsPackable>false</IsPackable> (add IsPackable too if missing):

<PropertyGroup>
  <IsPackable>false</IsPackable>
  <IsPublishable>false</IsPublishable>
</PropertyGroup>

Verify with the exact dotnet publish from that repo's Dockerfile (usually dotnet publish "<Solution>.sln" --no-restore -c Release -o out).
Confirm out/ has no test binaries: no Moq.dll, no *.Tests.dll, no coverlet.collector.deps.json.
Confirm the host *.deps.json has a single Microsoft.Extensions.DependencyModel expectation at the host version (e.g. 10.0.12).
Confirm tests still build and run (dotnet test).

---name: fix-dependency-modeldescription: Fixes AWS deploy crash "Could not load file or assembly 'Microsoft.Extensions.DependencyModel'" in Shine/Playon .NET services. Root cause is Dockerfile `dotnet publish` of the whole solution into one flat out/ folder — test projects (coverlet.collector) overwrite the host's DependencyModel. Fix by setting IsPublishable false on test projects. Use immediately when this exception, assembly-not-found for DependencyModel, or a coverlet/test-publish version clash appears. Do not add a Host PackageReference for DependencyModel.---# Fix Microsoft.Extensions.DependencyModel publish clash## Error```Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly'Microsoft.Extensions.DependencyModel, Version=10.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'```Serilog raises this while reading its configuration. It is a race: last writer to `out/` wins, so it only shows up after test-project or publish-order changes.## Root causeThe Dockerfile runs `dotnet publish` on the **whole solution** into a single flat `out/` folder that becomes the runtime image.The solution includes test projects. `coverlet.collector` ships `Microsoft.Extensions.DependencyModel` 8.0.2; the Host needs 10.x. Both write the same filename. When coverlet's copy wins, the host asks the CLR for assembly version `10.0.0.0` and gets `8.0.0.0`.Do **not** pin or add `Microsoft.Extensions.DependencyModel` on the Host csproj / `Directory.Packages.props`. That papers over the clash; the next test dependency can still overwrite `out/`.## Fix1. Find every test project (`*Tests*.csproj`, `*Test*.csproj`).2. Add `<IsPublishable>false</IsPublishable>` beside the existing `<IsPackable>false</IsPackable>` (add `IsPackable` too if missing):```xml<PropertyGroup> <IsPackable>false</IsPackable> <IsPublishable>false</IsPublishable></PropertyGroup>```3. Verify with the **exact** `dotnet publish` from that repo's Dockerfile (usually `dotnet publish "<Solution>.sln" --no-restore -c Release -o out`).4. Confirm `out/` has no test binaries: no `Moq.dll`, no `*.Tests.dll`, no `coverlet.collector.deps.json`.5. Confirm the host `*.deps.json` has a single `Microsoft.Extensions.DependencyModel` expectation at the host version (e.g. `10.0.12`).6. Confirm tests still build and run (`dotnet test`).

Frequently asked questions