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

Framework selector menu should show the friendly name of the framework #1674

Open
BillHiebert opened this issue Mar 3, 2017 · 4 comments
Open
Labels
Feature-Multi-Targeting Targeting and building for multiple frameworks. Triage-Approved Reviewed and prioritized
Milestone

Comments

@BillHiebert
Copy link
Contributor

BillHiebert commented Mar 3, 2017

  1. Create a new console application
  2. Cross-target by change to and specify a 2nd framework like net452. Save
  3. The debug dropdown will list the current active framework and a menu to change the selection

The menu shows the short names. Instead it should show the friendly name

@abpiskunov
Copy link
Contributor

I have a pending change that contains a component that can provide friendly target frameworks names obtained from Nuget API. Will let you know when i check it in.

@srivatsn srivatsn added the Bug label Mar 5, 2017
@srivatsn srivatsn added this to the 15.3 milestone Mar 5, 2017
@davkean
Copy link
Member

davkean commented Mar 6, 2017

I disagree that this should be done by the project system. This should be calculated during the build, for use both in the build, and in VS.

@abpiskunov
Copy link
Contributor

Build is too slow - what would you show in VS until build is not happened? We have 3 places now: editor top combobox, F5 framework selector and Solution explorer tree - all of them need friendly framework names and should be displayed when project just opened. If we wait for build and then update UI - too many flicks and bad UI design. I already have a component that talks to Nuget API and uses same Nuget assemblies build would use to determine frameworks , why not use it if we can?

@davkean
Copy link
Member

davkean commented Mar 7, 2017

By build here, I mean during evaluation in the same way that we calculate the full TFM.

@srivatsn srivatsn modified the milestones: 15.6, 15.3 May 11, 2017
@panopticoncentral panopticoncentral removed their assignment Sep 21, 2017
@Pilchie Pilchie modified the milestones: 15.5, 15.6 Oct 17, 2017
@Pilchie Pilchie added Area-New-Project-System Feature-Multi-Targeting Targeting and building for multiple frameworks. labels Dec 19, 2017
@Pilchie Pilchie modified the milestones: 15.6, Unknown Dec 19, 2017
@jjmew jjmew added the Triage-Approved Reviewed and prioritized label Jan 14, 2019
@drewnoakes drewnoakes removed the Bug label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature-Multi-Targeting Targeting and building for multiple frameworks. Triage-Approved Reviewed and prioritized
Projects
None yet
Development

No branches or pull requests

8 participants