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.

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

Figure out what to do with flavors #87

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

Figure out what to do with flavors #87

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-Feature Missing features from the legacy project system. Triage-Approved Reviewed and prioritized
Milestone

Comments

@davkean
Copy link
Member

davkean commented May 13, 2016

From @davkean on March 22, 2016 22:18

There's are lots of flavors build on top of csproj/msvbprj including Silverlight, Phone, Store, UWP, Portable and 3rd party flavors. We need to figure out what we are going to do with? Do they port? Or we do we come up a with a way that can they can flavor/extend the base CPS project system.

Copied from original issue: dotnet/roslyn#9982

@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

For those that are unlikely to be ported such as Web Application Projects, we'll want to see if we mimic flavoring similar to what csproj/projectaggregator did. For this to work however, we'll need the ability to override/extend the project node in CPS so that we can add csproj-based interfaces without requiring CPS to implement them directly.

@srivatsn srivatsn added this to the 1.0 (RC) milestone May 24, 2016
@srivatsn srivatsn modified the milestones: 1.0 RC, 1.1 Jul 1, 2016
@srivatsn srivatsn modified the milestone: 15.3 Mar 1, 2017
@davkean davkean added this to the 16.0 milestone Mar 19, 2017
@davkean davkean modified the milestones: 16.0, Backlog Dec 12, 2018
@jjmew jjmew added the Triage-Approved Reviewed and prioritized label Jan 14, 2019
@drewnoakes drewnoakes changed the title Project System: Figure out what to do with flavors Figure out what to do with flavors Apr 5, 2020
eric62369 pushed a commit to eric62369/project-system that referenced this issue Jul 10, 2020
…430.6 (dotnet#87)

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

No branches or pull requests

4 participants