dotnet / dotnet/project-system

`Rule.Default` is ignored for Launch Profiles

Open
#9,655 1 comment 0 reactions 0 assignees View on GitHub
Feature-Debugging Feature-Rules/Properties
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

## Visual Studio Version
2022 Preview

## Summary
I've created an `IRuleObjectProvider` for a custom Launch Profile following the guide at https://github.com/dotnet/project-system/blob/main/docs/repo/property-pages/how-to-add-a-new-launch-profile-kind.md. However, for any `StringProperty` or even `IntProperty`, the `Default` property is ignored.

## Steps to Reproduce

1. Follow the steps in https://github.com/dotnet/project-system/blob/main/docs/repo/property-pages/how-to-add-a-new-launch-profile-kind.md to create a custom Launch Profile
2. Assign a value to a `StringProperty.Default` property.
3. Launch the Launch Profile UI in Visual Studio, select the launch profile, and notice that the fields are not populated with the default.

## Expected Behavior
When creating a new Launch Profile using the `IRuleObjectProvider` API, and assigning values to the `Default` property of `StringProperty` and friends, when creating a new Launch Profile using the Visual Studio UI, then fields for each `Rule` should be populated with the value assigned to the `Default` property

## Actual Behavior
The Visual Studio Launch Profile UI should populate the Rule fields with the value assigned to each rule's `Default` property.

## User Impact
Users and developers are immensely annoyed.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.