How to debug "aspire publish" and "aspire deploy"

[Paulo Morgado (paulomorgado)]

How do I debug this?

When publishing a .NET project, how do I get a binlog for the publish?

[David Fowler (davidfowl)]

Are you talking about the binlog for individual .NET projects during a container publish? We don't have a way to specific other arguments.

[Paulo Morgado (paulomorgado)]

The binlog would be great.

And a marker property for the build to know that the publish is coming from Aspire to allow custom publishing.

[David Fowler (davidfowl)]

A binlog for the .NET projects right?

[Paulo Morgado (paulomorgado)]

A binlog for the .NET projects right?

Yes!

[Stephen Lautier (stephenlautier)]

Similar question to this, whats the proper way to debug aspire deploy within vs/vscode?
I want to test an aspire pipeline such as DockerSSHPipeline

[Adam Ratzman (adamint)]

With the Aspire 13.2 CLI and the most recent Aspire VS Code extension, you can execute > Aspire: Deploy app, > Aspire: Publish deployment artifacts, or > Aspire: Execute pipeline step (aspire do) to debug aspire deploy, aspire publish, and aspire do respectively.

[David Fowler (davidfowl)]

Adam Ratzman (@adamint) added support for debugging the deployment pipeline recently

[Paulo Morgado (paulomorgado)]

Which version and how?

[Adam Ratzman (adamint)]

It is currently only available using the daily CLI and vs code extension builds, until 13.2
https://github.com/dotnet/aspire/blob/main/docs/using-latest-daily.md#install-the-daily-cli--vs-code-extension