Skip to content

Clarify working directory assignment for project launch configurations #10681

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.

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

karolz-ms
Copy link
Member

Also move the project launch configuration description into its own section of the spec (this is why this change looks so big at first glance--but only the last paragraphs is new).

(spec only change, so omitting the full checklist)

Also move the project launch configuration description into its own section of the spec
@github-actions github-actions bot added the area-integrations Issues pertaining to Aspire Integrations packages label Jul 25, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR clarifies the working directory behavior for project launch configurations in the IDE execution specification. The main change involves reorganizing the documentation by moving the project launch configuration details into a dedicated section and adding explicit guidance about working directory assignment.

  • Reorganized project launch configuration documentation into its own section for better structure
  • Added clarification about working directory behavior for project execution
  • Enhanced inline comments to better describe the "project" launch configuration type


b. If the `launch_profile` property is set, the IDE should check whether the service project has a launch profile with the name equal to the value of `launch_profile` property. If such profile is found, it should serve as the base profile. If not, there is no base profile.

b. If `launch_profile` property is absent, the IDE should check whether the service project has a launch profile with the same name as the profile used to launch Aspire application host project. If such profile is found, it should serve as the base profile. Otherwise there is no base profile.
Copy link
Preview

Copilot AI Jul 25, 2025

Choose a reason for hiding this comment

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

There are two consecutive list items labeled 'b.' in the base profile determination rules. The second item should be labeled 'c.' for proper sequential ordering.

Suggested change
b. If `launch_profile` property is absent, the IDE should check whether the service project has a launch profile with the same name as the profile used to launch Aspire application host project. If such profile is found, it should serve as the base profile. Otherwise there is no base profile.
c. If `launch_profile` property is absent, the IDE should check whether the service project has a launch profile with the same name as the profile used to launch Aspire application host project. If such profile is found, it should serve as the base profile. Otherwise there is no base profile.

Copilot uses AI. Check for mistakes.

Copy link
Member

@tmat tmat left a comment

Choose a reason for hiding this comment

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

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-integrations Issues pertaining to Aspire Integrations packages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants