Skip to content

Unify ILRepack across plugin/workflow-activity/PdPackage#62

Open
zekelinAlex wants to merge 7 commits into
TALXIS:masterfrom
zekelinAlex:users/alexander.zekelin/unify-ilrepack
Open

Unify ILRepack across plugin/workflow-activity/PdPackage#62
zekelinAlex wants to merge 7 commits into
TALXIS:masterfrom
zekelinAlex:users/alexander.zekelin/unify-ilrepack

Conversation

@zekelinAlex
Copy link
Copy Markdown
Contributor

Before this, PdPackage and plugin/workflow-activity each ran ILRepack their own
way. Different NuGet (ilrepack vs ILRepack.Lib.MSBuild.Task), different
invocation, different switches, three copies of an
empty stub file. Same job, three implementations. This PR collapses them.
what changed:

  • the merge target lives in Tasks as TalxisMergeOutputAssembly (renamed from
    TalxisMergePluginDependencies since PdPackage uses it too). plugin,
    workflow-activity, and PdPackage each wire it onto AfterTargets="Build"
    themselves. Tasks doesn't auto-hook, so Solution/Pcf/CodeApp/ScriptLibrary
    don't get dragged in.

zekelinAlex and others added 7 commits April 26, 2026 13:26
The exclusion list claimed to skip Microsoft.Xrm.Sdk* (per README and
header comment) but only filtered three exact filenames in practice:
Microsoft.Xrm.Sdk, .Deployment, .Workflow. Any future or third-party
Microsoft.Xrm.Sdk.<x>.dll that ended up in OutDir would be merged into
the plugin assembly and cause runtime version clashes inside the
Dataverse sandbox.

Replace the two specific Deployment/Workflow entries with a
StartsWith('Microsoft.Xrm.Sdk.') prefix check covering all sub-
namespaces. Exact 'Microsoft.Xrm.Sdk' (no trailing dot) stays as its
own entry so the base assembly is still excluded.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant