Skip to content

[docs] Document DotnetProjectResource publish limitation #1501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aspire-repo-bot wants to merge 1 commit into
base: release/13.5
Choose a base branch
from
+16 −0
Open

[docs] Document DotnetProjectResource publish limitation #1501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-host.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,6 +185,22 @@ await builder.build().run();

The resource is added as an [`ExecutableResource`](/app-host/executable-resources/) rather than a `ProjectResource`, so it doesn't need to be referenced from the AppHost's own solution. Before the resource starts, Aspire validates that the path resolves to a `.csproj` or `.cs` file (or a directory containing a single `.csproj`) and, for file-based apps, that the active .NET SDK version is 10 or later.

## Publishing

Automatic project publishing for `DotnetProjectResource` isn't currently supported. A plain
`DotnetProjectResource` causes `aspire publish` and `aspire deploy` to fail with an actionable error
instead of emitting an `executable.v0` manifest containing machine-local paths.
Comment thread
karolz-ms marked this conversation as resolved.

Use one of these alternatives:

- Use `AddProject<TProject>(...)` for a project referenced by a C# AppHost.
- Use `AddCSharpApp(...)` / `addCSharpApp(...)` for a path-based project or file-based app that
should use standard .NET project publishing.
- Call `PublishAsDockerFile(...)` / `publishAsDockerFile(...)` to configure container publishing

@adamint Adam Ratzman (adamint) Aug 15, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we mention that this requires an existing Dockerfile in the project directory? PublishAsDockerFile() configures a Dockerfile build; without one this alternative just moves the user to another publish failure.

explicitly.
- Call `ExcludeFromManifest()` / `excludeFromManifest()` when the resource is intentionally
available only during local orchestration.

## See also

- [.NET documentation](https://learn.microsoft.com/dotnet/)
Expand Down
Loading