TALXIS.DevKit.Build.Dataverse.PdPackage 1.7.0

TALXIS.DevKit.Build.Dataverse.PdPackage

MSBuild integration for Power Platform Package Deployer (PD) packages. Wraps Microsoft.PowerApps.MSBuild.PDPackage, adds ILRepack-based assembly merging for the deployment package DLL, and provides Configuration Migration Tool (CMT) package discovery, metadata merging, and zipping.

Installation

<PackageReference Include="TALXIS.DevKit.Build.Dataverse.PdPackage" Version="0.0.0.1" PrivateAssets="All" />

Or use the SDK approach:

<Project Sdk="TALXIS.DevKit.Build.Sdk/0.0.0.1">
  <PropertyGroup>
    <ProjectType>PdPackage</ProjectType>
  </PropertyGroup>
</Project>

How It Works

Microsoft PDPackage import

Props and targets from Microsoft.PowerApps.MSBuild.PDPackage are imported automatically. The version is controlled by PdPackageMsBuildVersion.

Defaults for ProjectReference

All ProjectReference items default to ReferenceOutputAssembly=false via ItemDefinitionGroup. PDPackage projects reference other projects (e.g. Solution) purely for build ordering and packaging, not to consume their output assemblies as compile-time references. Override per-reference by explicitly setting ReferenceOutputAssembly="true".

.NET Framework references

System.ComponentModel.Composition is automatically referenced when targeting .NET Framework. This is required by Microsoft.CrmSdk.XrmTooling.PackageDeployment (MEF / IImportPackageExtension).

Project reference filtering

_DetectPdProjectReferenceTypes probes all ProjectReference items for GetProjectType. Solution-type references have ReferenceOutputAssembly set to false so their DLLs are not included in the package output.

ImportConfig auto-generation

ImportConfig.xml is not required to exist in the project. If <AssetsSrcDirectory>ImportConfig.xml is missing, a skeleton (<configdatastorage> with empty <solutions>, <filestoimport>, <filesmapstoimport>) is generated in $(IntermediateOutputPath)<FolderName>/ImportConfig.xml before MSBuild validation runs, and @(PdImportConfig) is rewired to point at it. <FolderName> is read from the GetImportPackageDataFolderName property of any ImportExtension-derived class found in the project's top-level .cs files (default PkgAssets).

When AutoGeneratePdImportConfig is true (default) and the source ImportConfig.xml contains no <configsolutionfile> entries, the <solutions> section is generated automatically from the project's solution references. Both <ProjectReference> items pointing at Solution projects and <PackageReference> items pointing at pp-solution NuGet packages are picked up, and each one produces a <configsolutionfile> entry with requiredimportmode="async".

The generated entries appear in the same order as the references are declared in the .csproj file, walking <PackageReference> and <ProjectReference> items in document order (interleaved). A PackageReference is matched by its package id; a ProjectReference is matched by the csproj file name (without extension), which by convention equals the solution unique name. Any <configsolutionfile> element that can't be matched against a csproj reference is moved to the end while keeping its relative position.

If you ship a hand-written PkgAssets/ImportConfig.xml with explicit <configsolutionfile> entries, auto-generation is skipped entirely and your file is used as-is.

Assembly merge

AssemblyMergeDependencies (runs after Build via _AssemblyMergePackageDependenciesAfterBuild) merges dependency DLLs into the main output assembly using the shared ILRepack engine from TALXIS.DevKit.Build.Dataverse.Tasks. PdPackage defaults to a different exclude list than Plugin/WorkflowActivity — Newtonsoft.Json is not excluded because the package-deployer runtime doesn't provide it. Can be disabled with <AssemblyMergeSkip>true</AssemblyMergeSkip>.

CMT package discovery

DiscoverCmtPackages scans for folders containing [Content_Types].xml with sibling data.xml and data_schema.xml. Supports include/exclude filtering via IncludedCmtPackages/ExcludedCmtPackages.

CMT package zipping

_ZipCmtPackagesAfterBuild (runs after Build) zips each discovered CMT package directory into CmtPackageOutputDir.

CMT metadata merging

_PrepareCmtMetadataBeforePublish merges data.xml and data_schema.xml from all CMT packages into a single combined package, generates [Content_Types].xml, zips it, and appends a reference to ImportConfig.xml.

Publishing and NuGet packing

dotnet publish is the primary build command. It publishes the project, generates the .pdpkg.zip via GeneratePdPackage, and then automatically runs Pack to produce a .nupkg containing the .pdpkg.zip (controlled by GeneratePackageOnPublish).

MSBuild Properties

PDPackage

Assembly merge

Validation

CMT packages

CMT metadata merge

Related Packages

• Depends on: Microsoft.PowerApps.MSBuild.PDPackage, ILRepack.Lib.MSBuild.Task, TALXIS.DevKit.Build.Dataverse.Tasks
• Typically references: TALXIS.DevKit.Build.Dataverse.Solution projects