TALXIS.DevKit.Build.Dataverse.Solution 1.1.0

TALXIS.DevKit.Build.Dataverse.Solution

MSBuild integration for building complete Dataverse solutions. Orchestrates the entire solution build pipeline: discovers and builds referenced Plugin, WorkflowActivity, ScriptLibrary, CodeApp, and PCF projects; patches solution XML with version, publisher, and managed state; supports manual invocation of schema validation targets for solution metadata against XSD/JSON schemas; runs the PAC solution packager to produce a .zip file; and supports dotnet pack to generate a NuGet package containing the solution zip.

Installation

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

Or use the SDK approach:

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

How It Works

The package sets ProjectType to Solution and imports Microsoft.PowerApps.MSBuild.Solution targets. The build pipeline executes in the following order:

1. Component discovery

ProbePluginLibraries, ProbeScriptLibraries, ProbeCodeApps, and ProbeWorkflowActivityLibraries call GetProjectType on all ProjectReference items to classify them by component type. ScriptLibrary and CodeApp references are removed from @(ProjectReference) after discovery so the standard .NET ResolveProjectReferences pipeline does not build them a second time -- they are built explicitly in the next step.

2. Component builds

BuildPluginLibraries, BuildScriptLibraries, BuildCodeApps, and BuildWorkflowActivityLibraries compile each referenced component project before CopyCdsSolutionContent.

3. Component metadata generation

• Plugin assemblies -- EnsurePluginAssemblyDataXml generates .data.xml files under PluginAssemblies/.
• Workflow activities -- EnsureWorkflowActivityAssemblyDataXml generates .data.xml for workflow activity assemblies.
• Script libraries -- CopyScriptLibrariesToWebResources resolves web resource names with the publisher prefix, generates .data.xml, and registers root components in Solution.xml.
• Code apps -- PrepareCodeAppsSources generates .meta.xml via GenerateCodeAppMetaXml, adds root components (Type 300) to Solution.xml, and ensures the CanvasApps node exists in Customizations.xml.

4. Solution XML patching

PatchSolutionXml writes Version (use ApplyVersionNumber instead, see below), Managed, PublisherName, and PublisherPrefix into Solution.xml (all optional).

5. PAC override and versioning

ProcessCdsProjectReferencesOutputs replaces the Microsoft default to filter ScriptLibrary, CodeApp, and WorkflowActivity references from PAC processing. Then GenerateVersionNumber and ApplyVersionNumber patch the version across all solution metadata.

6. Schema validation (manual)

ValidateSolutionComponentSchema validates all solution XML files against 22 bundled XSD schemas and JSON flows against a JSON schema. Validation runs in batch mode -- all errors are collected before failing the build, with MSBuild-canonical error format for IDE click-through.

7. Solution packaging

PowerAppsPackage invokes the PAC solution packager to produce the output .zip.

8. NuGet packing

dotnet pack produces a .nupkg with the solution .zip under content/solution/.

MSBuild Properties

General

Solution metadata

Paths

Web resources and PCF

Validation

Schema validation via ValidateSolutionComponentSchema is not wired automatically -- invoke it manually (e.g. dotnet build -t:ValidateSolutionComponentSchema). No skip property is needed.

Related Packages

• Depends on: TALXIS.DevKit.Build.Dataverse.Tasks, Microsoft.PowerApps.MSBuild.Solution
• Discovers and builds: Plugin, WorkflowActivity, ScriptLibrary, CodeApp, and Pcf projects via ProjectReference