Skip to content

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

@SigrunO

Description

@SigrunO

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions