developer-delphi-windows-store-publishing_V1.0.0

Publish Delphi Windows Store apps through a complete MSIX workflow.

Updated Jan 6, 2026

Search Tags:#msix #store-submission #partner-center #delphi #windows-store #wack #iarc

Ready to run

npx skills add https://github.com/cslsoftwares/ParamentersORM --skill developer-delphi-windows-store-publishing-v1-0-0

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: developer-delphi-windows-store-publishing_V1.0.0
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/developer-delphi-windows-store-publishing_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill developer-delphi-windows-store-publishing-v1-0-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing Delphi Windows Store apps involves a multi-step, error-prone process that spans Partner Center account setup, product name reservation, Package Identity extraction, .dproj configuration for MSIX, WACK certification, IARC classification, metadata submission, staged rollout, and versioned updates. This Skill consolidates the end-to-end publishing workflow into a repeatable guide that reduces errors and accelerates time-to-store adoption.

Core Features & Use Cases

End-to-end publishing workflow: covers account setup, name reservation, Package Identity extraction, and .dproj integration for MSIX.
Quality & compliance checks: WACK certification, IARC classification, and policy-aware metadata entry to prevent submission rejections.
Release and update management: steps for new submissions, staged rollout configuration, versioning, and automatic user delivery.
Use Case: a Delphi developer team publishing Windows desktop apps to the Microsoft Store with repeatable processes.

Quick Start

Begin by signing into Partner Center, reserve your app name, copy Package Identity into your .dproj, build a Release MSIX, run WACK, and submit to the Store.

Frequently Asked Questions about developer-delphi-windows-store-publishing_V1.0.0

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

FAQPage Schema

How do I publish a Delphi app to the Windows Store using MSIX?▼

Delphi Windows Store publishing requires a complete MSIX workflow: Partner Center enrollment, name reservation, Package Identity extraction, .dproj integration, WACK certification, IARC classification, and final store submission. This consolidated workflow reduces errors and accelerates time-to-store adoption.

What is the Package Identity and how do I integrate it into a Delphi .dproj file?▼

Package Identity is a unique identifier reserved in Partner Center for your app. You extract this identity and integrate it into your Delphi .dproj configuration to properly align your project for MSIX packaging and Windows Store submission.

Why does my Windows Store submission fail WACK certification for Delphi apps?▼

WACK certification failures often stem from metadata errors, versioning mismatches, or policy non-compliance. Enforcing best practices for metadata entry, eligibility checks, and IARC classification before staging prevents common Windows Store submission rejections.

Do I need an IARC classification to publish a Delphi desktop app to the Microsoft Store?▼

Yes, IARC classification is required for Microsoft Store submission. It evaluates your app's content to determine age ratings, which is a mandatory step in the quality and compliance checks before your Delphi app can be approved.

What's the best way to manage staged rollouts and versioned updates for Windows Store apps?▼

The best way to manage staged rollouts and versioned updates is to follow a structured release workflow. This involves configuring staged rollout settings in Partner Center and enforcing strict versioning rules to ensure automatic user delivery of new submissions.