export-package

Export Directum RX .dat packages from Git with C# compilation via DeploymentToolCore.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill export-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-package
Source: https://github.com/dunaevdmitriys-dev/directum-mcp-server/tree/main/skills/export-package
Command: npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill export-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone process of building and packaging Directum RX deployment .dat files by exporting them directly from your Git repository with full C# compilation.

Core Features & Use Cases

  • Git-to-.dat export with compilation: Creates a .dat package directly from source code using DeploymentToolCore (dt export-package), performing full Roslyn C# compilation (unlike simple zipping).
  • Config-driven packaging: Uses an XML configuration (DevelopmentPackageInfo) to define modules, IDs (from Module.mtd NameGuid), names, versions, and inclusion of assemblies/sources.
  • Deployment lifecycle utilities: Supports follow-up workflows such as merging multiple packages and version increment/set operations.

Quick Start

Ask the AI to export your Directum .dat package from the Git repository by running dt export_package with an XML export configuration and saving the resulting .dat to your desired output path.

Frequently Asked Questions about export-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compile C# sources and export a .dat package directly from a Git repository?

You can export a .dat package from Git by running dt export_package with an XML configuration, which triggers DeploymentToolCore to perform full Roslyn C# compilation and output the deployable file. This provides production-like compilation rather than simple archive zipping.

What is the difference between a compiled .dat package and a standard source archive?

A compiled .dat package uses Roslyn C# compilation to produce deployable binaries, whereas a standard archive simply zips source files without building. This ensures the package is ready for Directum RX environments.

Do I need a specific XML configuration to build a Directum RX deployment package?

Yes, you need a prepared DevelopmentPackageInfo XML configuration to define modules, IDs from Module.mtd NameGuid, names, versions, and assembly inclusions. This XML file is required to run the dt export_package command successfully.

What environment setup is required to run Directum RX package export workflows?

You need a valid DirectumLauncher setup, repository access to source and metadata files like PackageInfo.xml and Module.mtd, and functioning platform services allowing DeploymentToolCore to connect before running the export_package command.

Can I merge multiple .dat packages or update their versions after exporting?

Yes, after exporting your .dat package, you can use deployment lifecycle utilities to merge multiple packages together and perform version increment or set operations. This supports follow-up build-and-package workflows for Directum RX modules.