dds-build-errors

Diagnose Directum DDS build and import failures by matching error text to root-cause fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly identify the real cause of Directum DDS build/import failures instead of guessing, by mapping common error text to targeted fixes.

Core Features & Use Cases

  • Error-to-fix lookup: Matches build, import, runtime, and UI issues against a curated table of Directum DDS error patterns.
  • Anti-loop guidance: Prevents repeating the same wrong fix by enforcing a “break the error cycle” rule.
  • Practical remediation steps: Provides concrete actions such as adjusting metadata (e.g., SourceTableName, IsDisplayValue), fixing namespace/override rules, and handling satellite DLL/runtime deployment issues.
  • Use case: You run a DDS build after changes and see errors like Missing area or NullReferenceException, then use this Skill to apply the correct metadata/code-level correction and re-run validation.

Quick Start

Ask the AI to resolve your DDS build failure by telling it the exact full error text you see and confirming you have already checked whether you tried the same fix previously.

Frequently Asked Questions about dds-build-errors

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

FAQPage Schema
How do I diagnose Directum DDS build errors after making metadata changes?

To diagnose Directum DDS build errors, match the exact full error text to a curated root-cause table to identify the specific metadata or code-level issue, then apply the corresponding targeted fix and re-run validation.

What causes NullReferenceException during a Directum DDS build or deployment?

A NullReferenceException during a Directum DDS build is typically caused by incorrect metadata settings or post-publication runtime issues, which you can resolve by applying metadata fixes like adjusting SourceTableName or IsDisplayValue.

How do I fix C# compilation errors when importing a .dat file in Directum DDS?

Fix C# compilation errors during Directum DDS .dat imports by checking namespace and override rules, verifying satellite DLL runtime deployment, and matching the exact error text to known root-cause table fixes.

Why does my Directum DDS DeploymentToolCore exit with an error code and how do I fix it?

DeploymentToolCore exit-code troubleshooting involves matching the specific exit code to known Directum DDS build or import failure patterns, preventing repeated wrong fixes by following the anti-loop rule, and validating outcomes with /validate-all.

How do I troubleshoot Directum DDS UI metadata problems after publication?

Troubleshoot Directum DDS UI metadata problems after publication by identifying the exact error message, applying metadata corrections such as adjusting IsDisplayValue, and running /validate-all to confirm the runtime issue is resolved.

What should I do if the same Directum DDS build fix keeps failing repeatedly?

If the same Directum DDS build fix keeps failing, apply the anti-loop rule by breaking the error cycle, ensuring you are using the full exact error text for lookup, and verifying the correct metadata adjustment before re-running validation.