pac solution pack should support plugin packages

[mathiasbl]

Been trying to replace our own built nuget package by using the mapping file functionality during the pac solution pack command but it's not getting picked up.

Is this feature supported or still in the works.

[mathiasbl]

@JimDaly sorry, actually meant the pac solution pack command.

[JimDaly]

OK. I deleted my comment.

[jworbis]

Hi,
I was about to ask the same. I was trying to map my pluginpackages but couldn't get it to work. Is there anything planned for the future? Or is there a workaround? I didn't have the time to test it completely, I somehow managed to create a map xml that deletes the nuget package on pac solution unpack, but I had no luck mapping my build outputs into the solution.

Thanks!

[mathiasbl]

@jworbis They added an example in the docs.

<FileToFile
    map="pluginpackages\cr886_PluginPackageTest\package\cr886_PluginPackageTest.nupkg"
    to="myplg\bin\Debug\myplg.1.0.0.nupkg" />

https://learn.microsoft.com/en-us/power-platform/alm/solution-packager-tool

[ferodom]

I am having an issue when unpacking plugin nuget packages, if there is a map to a file that is not part of the solution I get the error below. Note Having multiple plugin directives work just fine, the tool just skips them. Note: I prefer to have just one map.xml since I work with multiple solutions.

Error: Value cannot be null.
Parameter name: key

this is my map.xml

[SakthiChandra]

I'm encountering the same error when unpacking the solution, particularly when plugin packages are included in my filemap XML. How can I resolve this issue?

[janis-veinbergs]

I founda workaround - move FileToFile plugin package BEFORE all mappings. In my case it was after some other plugins and I got this error. Once moved to top, unpack works. Screams like a bug to me.

[ferodom]

I tried that as well and it worked for me as long as I had one plugin package, Once I added the other then it broke again. Definitely a bug. Can we get some help?