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

Project System: Determine what, if any, of VSLangProj we should implement #10086

Closed
davkean opened this issue Mar 24, 2016 · 2 comments
Closed

Project System: Determine what, if any, of VSLangProj we should implement #10086

davkean opened this issue Mar 24, 2016 · 2 comments
Labels
0 - Backlog Feature Request
Milestone
2.0 (Preview 4)

Comments

@davkean
Copy link
Member

davkean commented Mar 24, 2016

VSLangProj has fairly extensive usage across VS components and 3rd party extensions. We should consider what of the APIs we should implement.
@davkean davkean added this to the 2.0 (Preview 3) milestone Apr 11, 2016
@davkean
Copy link
Member Author

davkean commented Apr 20, 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
Open
@davkean
Copy link
Member Author

davkean commented May 13, 2016

This issue was moved to dotnet/project-system#97

@davkean davkean closed this as completed May 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - Backlog Feature Request
Projects
None yet
Milestone
2.0 (Preview 4)
Development

No branches or pull requests
2 participants
@srivatsn @davkean