microsoft / microsoft/powerplatform-vscode

pac solution pack with mapping file does not honor wildcards in file to file mapping

Open
#1,231 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
277
Forks
60
Avg merge
1d 1h
Merged PRs (30d)
14

Description

I am trying to pack a solution with a mapping file for JavaScript and plugin dlls. The mapping for the plugin dlls does not work with folder wildcards in FileToFile mapping. This worked well in older versions of the solution packager. The latest solution packager has the same bug.

<FileToFile` map=\"PluginAssemblies\**\this.dll\" to="..\..\Plugins\**\that.dll" />

Calling pac solution pack with such a mapping ends up with the following error message, even though the file exists.

Mapped file '..\..\Plugins\**\that.dll' doesn't exist. Skipping.

Replacing ** in the mapping by the correct folder path (e.g. Debug\net462) makes the packager work, but is not desirable.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with pac solution pack and the shown FileToFile mapping, using the wildcard path and the explicit Debug\net462 path for comparison. Trace how folder wildcards are resolved and confirm that the mapped plugin DLL is found; done means the wildcard mapping packs successfully without requiring a hard-coded folder.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.