microsoft / microsoft/powerplatform-vscode
`pac solution add-reference` does not work with Dependent Assembly plugin project
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 60
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 14
Description
Calling pac solution pack (version: 1.19.4+gfbe2fd6) with mapping file does not map pluginpackages. To reproduce:
pack plugin inita new plugin and build it- open plugin registration tool
pac tool prtand choose "Register New Package" to upload the nupkg created at step 1 - Ensure the Plugin Package has been added to your solution, export and unpack the solution using
pac solution exportandpac solution unpack - pack the solution using
pac solution pack -m mapping.xml -etcetcwhere the mapping.xml file contains the an entry similar tot he following:
<FileToFile
map="prefix_XXXXXXXX.nupkg"
to="..\..\PATH_TO_PLUGIN_PROJECT\bin\Release\XXXXXXXX.1.0.0.nupkg"
/>
or
<FileToFile
map="pluginpackages\prefix_XXXXXXXX\package\prefix_XXXXXXXX.nupkg"
to="..\..\PATH_TO_PLUGIN_PROJECT\bin\Release\XXXXXXXX.1.0.0.nupkg"
/>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the workflow using pack plugin init, pac solution export, pac solution unpack, and pac solution pack -m mapping.xml. Compare the two FileToFile mappings for the plugin package and determine what mapping behavior is expected; done means the dependent assembly plugin package is included correctly when the solution is packed.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100