How do I install the Aspire Maui Bundle Shim skill?

Run npx skillmds@latest add davidortinau/aspire-maui-bundle-shim in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Aspire Maui Bundle Shim skill do?

Skill: Aspire.Hosting.Maui bundle-name shim (MSBuild post-build) It is listed under Coding & Dev Tools on SkillMD.

Is Aspire Maui Bundle Shim safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aspire Maui Bundle Shim?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aspire Maui Bundle Shim free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aspire Maui Bundle Shim?

davidortinau (@davidortinau) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aspire Maui Bundle Shim by davidortinau

Name: Aspire Maui Bundle Shim
Author: davidortinau

File contents

Skill: Aspire.Hosting.Maui bundle-name shim (MSBuild post-build)

When to use

A .NET MAUI project orchestrated by Aspire silently fails to launch (resource state goes to Exited / Failed, no console logs, exit code 1) and the project's <ApplicationTitle> differs from $(MSBuildProjectName).

Cause: Aspire.Hosting.Maui (≤ 13.3.0-preview) computes the bundle path as bin/$(Configuration)/$(TargetFramework)/<rid>/$(MSBuildProjectName).app and calls open -a on it. The MAUI build actually produces $(ApplicationTitle).app, so the file isn't found.

Fix (Mac Catalyst)

Add this target to the MAUI project's csproj:

<Target Name="_CreateAspireBundleNameSymlink"
        AfterTargets="Build"
        Condition="'$(TargetFramework)' == 'net10.0-maccatalyst' And '$(_AppBundleName)' != '' And '$(_AppBundleName)' != '$(MSBuildProjectName)'">
  <PropertyGroup>
    <!-- $(OutputPath) already includes the RID for Mac Catalyst. Do NOT append $(RuntimeIdentifier). -->
    <_AspireBundleDir>$(OutputPath)</_AspireBundleDir>
    <_AspireBundleSourceApp>$(_AspireBundleDir)$(_AppBundleName).app</_AspireBundleSourceApp>
    <_AspireBundleAliasApp>$(_AspireBundleDir)$(MSBuildProjectName).app</_AspireBundleAliasApp>
  </PropertyGroup>
  <Exec Condition="Exists('$(_AspireBundleSourceApp)')"
        Command="ln -sfn '$(_AppBundleName).app' '$(_AspireBundleAliasApp)'"
        WorkingDirectory="$(MSBuildProjectDirectory)" />
</Target>

Key facts

$(_AppBundleName) is set by the Xamarin/MAUI Shared SDK target _GenerateBundleName and reflects the actual produced bundle name.
For Mac Catalyst, $(OutputPath) is already bin/$(Config)/net10.0-maccatalyst/$(RuntimeIdentifier)/. Appending $(RuntimeIdentifier) again produces a doubled-RID path and the Exists() guard silently skips the Exec. Always check with dotnet build -v:diag and grep for the target name.
ln -sfn is idempotent — safe on rebuild.
Survives dotnet clean because the target is part of the normal Build chain.

iOS / other Apple platforms

Same pattern applies; gate the target on the appropriate TFM. iOS device builds may need the symlink in the Payload/ IPA directory instead of the plain .app directory — verify per-platform path before extending blindly.

Remove when

Aspire.Hosting.Maui exposes a bundle-name override API. Track upstream; delete the target and its XML comment when available.

---name: aspire-maui-bundle-shimdescription: Skill: Aspire.Hosting.Maui bundle-name shim (MSBuild post-build)---# Skill: Aspire.Hosting.Maui bundle-name shim (MSBuild post-build)## When to useA .NET MAUI project orchestrated by Aspire silently fails to launch (resourcestate goes to Exited / Failed, no console logs, exit code 1) and the project's`<ApplicationTitle>` differs from `$(MSBuildProjectName)`.Cause: `Aspire.Hosting.Maui` (≤ 13.3.0-preview) computes the bundle path as`bin/$(Configuration)/$(TargetFramework)/<rid>/$(MSBuildProjectName).app` andcalls `open -a` on it. The MAUI build actually produces`$(ApplicationTitle).app`, so the file isn't found.## Fix (Mac Catalyst)Add this target to the MAUI project's csproj:```xml<Target Name="_CreateAspireBundleNameSymlink" AfterTargets="Build" Condition="'$(TargetFramework)' == 'net10.0-maccatalyst' And '$(_AppBundleName)' != '' And '$(_AppBundleName)' != '$(MSBuildProjectName)'"> <PropertyGroup>  <_AspireBundleDir>$(OutputPath)</_AspireBundleDir> <_AspireBundleSourceApp>$(_AspireBundleDir)$(_AppBundleName).app</_AspireBundleSourceApp> <_AspireBundleAliasApp>$(_AspireBundleDir)$(MSBuildProjectName).app</_AspireBundleAliasApp> </PropertyGroup> <Exec Condition="Exists('$(_AspireBundleSourceApp)')" Command="ln -sfn '$(_AppBundleName).app' '$(_AspireBundleAliasApp)'" WorkingDirectory="$(MSBuildProjectDirectory)" /></Target>```## Key facts- `$(_AppBundleName)` is set by the Xamarin/MAUI Shared SDK target `_GenerateBundleName` and reflects the actual produced bundle name.- For Mac Catalyst, `$(OutputPath)` is already `bin/$(Config)/net10.0-maccatalyst/$(RuntimeIdentifier)/`. Appending `$(RuntimeIdentifier)` again produces a doubled-RID path and the `Exists()` guard silently skips the `Exec`. Always check with `dotnet build -v:diag` and grep for the target name.- `ln -sfn` is idempotent — safe on rebuild.- Survives `dotnet clean` because the target is part of the normal Build chain.## iOS / other Apple platformsSame pattern applies; gate the target on the appropriate TFM. iOS devicebuilds may need the symlink in the `Payload/` IPA directory instead of theplain `.app` directory — verify per-platform path before extending blindly.## Remove whenAspire.Hosting.Maui exposes a bundle-name override API. Track upstream;delete the target and its XML comment when available.

Frequently asked questions

Aspire Maui Bundle Shim