Skip to content
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

Jump to bottom

Determine what, if any, of VSLangProj we should implement #97

Open
davkean opened this issue May 13, 2016 · 1 comment
Open

Determine what, if any, of VSLangProj we should implement #97

davkean opened this issue May 13, 2016 · 1 comment
Labels
Needs-CPS-work Changes are needed in the closed-source Common Project System (CPS) repo. Parity-Legacy-API Missing or behavior differences in APIs from the legacy project system. Parity-Legacy-Feature Missing features from the legacy project system. Triage-Approved Reviewed and prioritized
Milestone
Backlog

Comments

@davkean
Copy link
Member

davkean commented May 13, 2016

From @davkean on March 24, 2016 22:33

VSLangProj has fairly extensive usage across VS components and 3rd party extensions. We should consider what of the APIs we should implement.

Copied from original issue: dotnet/roslyn#10086
@davkean davkean added Area-Project System Parity-Legacy-Feature Missing features from the legacy project system. Needs-CPS-work Changes are needed in the closed-source Common Project System (CPS) repo. labels May 13, 2016
@davkean
Copy link
Member Author

davkean commented May 13, 2016

CPS will either need to implement said interfaces or provide us a mechanism where we can add them ourselves (either via COM aggregation, or by being able to wrap these objects, such as configurations, project node, etc).

@davkean davkean mentioned this issue May 13, 2016
Closed
@srivatsn srivatsn modified the milestone: 1.0 (Preview 4) May 24, 2016
@srivatsn srivatsn modified the milestones: 1.0 Preview 4, 1.0 RC, 1.1 Jun 24, 2016
@srivatsn srivatsn modified the milestones: 15.6, 15.3 May 4, 2017
@srivatsn srivatsn modified the milestones: 16.0 Preview1, 15.5 Jul 28, 2017
@basoundr basoundr removed their assignment Sep 27, 2017
@davkean davkean removed this from the 15.7 milestone Mar 2, 2018
@davkean davkean added this to the Unknown milestone Mar 2, 2018
@davkean davkean added Parity-Legacy-API Missing or behavior differences in APIs from the legacy project system. and removed Parity-Legacy-Feature Missing features from the legacy project system. labels Jul 25, 2018
@jjmew jjmew added Triage-Approved Reviewed and prioritized and removed Triage-Approved Reviewed and prioritized labels Jan 14, 2019
@panopticoncentral panopticoncentral added Parity-Legacy-Feature Missing features from the legacy project system. and removed Parity-Legacy-Feature Missing features from the legacy project system. labels Feb 14, 2019
@drewnoakes drewnoakes changed the title Project System: Determine what, if any, of VSLangProj we should implement Determine what, if any, of VSLangProj we should implement Apr 5, 2020
eric62369 pushed a commit to eric62369/project-system that referenced this issue Jul 10, 2020
@dotnet-maestro
Update dependencies from https://github.com/dotnet/arcade build 20190…
864a937 
…510.2 (dotnet#97)

- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19260.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-CPS-work Changes are needed in the closed-source Common Project System (CPS) repo. Parity-Legacy-API Missing or behavior differences in APIs from the legacy project system. Parity-Legacy-Feature Missing features from the legacy project system. Triage-Approved Reviewed and prioritized
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
8 participants
@srivatsn @drewnoakes @panopticoncentral @davkean @tannergooding @tmeschter @basoundr @jjmew