Update/Install re-adds content items if they have been modified to EmbeddedResource

[pms1969]

If you have a package with content, and you want that content then to become an embedded resource (you switch it in VS), a paket update or paket install will add the file a second time to the project (i.e. it appears twice in VS).

Just wondering if this is a bug, or if there is some paket.dependencies jigpokery I can do to stop this.

Repro steps

As described above.

1. add a package that has content.
2. open solution in VS
3. change content file to EmbeddedResource in properties pane
4. run paket update

Expected behavior

I'd expect there to be only 1 file, or there to be a way in paket.dependencies to ensure that the content is embeded, but given that you may only want to do this to certain files, maybe not adding it again would be preferable.

Actual behavior

file appears twice in the project.

Known workarounds

unknown

Related information

• Operating system = Windows
• Branch = Paket version 2.58.6.0
• .NET Runtime 4.5

[forki]

yeah I guess this is not supported yet. we would need a repro sample ad then we can try to make that work

[forki]

/cc @sergey-tihon

[sergey-tihon]

Yes, it is not supported, would be nice to know package name and type of content.

Now packet identify build action based on content type and then add to the project.
If you change build action to EmbeddedResource on the next install\update packet cannot find file (that he added) and add it once again with default build action.

[pms1969]

Can't get you a repro right now, but will try to remember to do it over the weekend.

On a related note, this is very much like (#1555). Given both those issues,is it perhaps better to not manage content files from paket, except to copy or not copy them to the solution, and add if not there? Would solve both issues, but there may be a need/use case that I'm unaware of.

[github-actions]

🤖 This is an automated response from Repo Assist.

This issue is from 2016 and describes behavior specific to legacy (non-SDK-style) .csproj/packages.config-era project handling, where Paket managed Content/EmbeddedResource item groups directly in the project file. Modern .NET SDK-style projects (the vast majority in use today) don't have this failure mode, since Paket no longer needs to duplicate content-item entries the same way, and Visual Studio's "convert to EmbeddedResource" action operates on MSBuild item metadata rather than triggering a duplicate insert on the next paket install.

There's been no reproduction or follow-up activity in over 7 years, and no evidence this still affects current SDK-style projects. Recommend closing as stale/unlikely-to-reproduce on modern project formats, unless someone can confirm it still happens today.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
_{Comment /repo-assist to run again}

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38