dotnet / dotnet/project-system

Export ProjectConfig as ProjectConfigurationProperties once ComAggregation is available over ProjectConfig

Open
#2,174 1 comment 0 reactions 0 assignees View on GitHub
Blocked Parity-Legacy-Feature Triage-Approved
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

This work has 2 tasks and a required work from CPS.

Summary: There are 2 ways to get a Project Configuration Properties. One is through `IVSHierarchy` using `IVsCfgBrowseObject` and the other is through Automation via DTE. Today, different objects are returned for each of this mechanism. `IVsHierarchy` returns `ProjectConfig` and Automation returns `CSharp/VisualBasicProjectConfigurationProperties`(#2172). But we would like to return the same object for both of these mechanisms(Old Project system does this as well). To make this happen, we will need CPS to enable Com Aggregation over the Project Config. Once we have that in place, we have 2 tasks.

- [ ] Export an object which will be Com Aggregated over Project Config
- [ ] Introduce a component which imports ProjectConfig and returns it as the Automation Object

At this point, we will be returning the aggregated `ProjectConfig` object for both `IVsCfgBrowseObject` and Automation.

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.