Add TFMs to top level package properties grid (partial fix for 587 for RTM) #1515
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@srivatsn in case you get this approved here is a change... |
|
@natidea @dotnet/project-system |
|
Let's retarget this to post-dev15. This was rejected as a bar-check. |
srivatsn
approved these changes
Mar 24, 2017
|
@abpiskunov Is this relevant anymore? |
|
No, after we check in #1880 these properties would be not needed, i will close it for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Customer scenario
Since we can not do full support for showing multiple TFMs in UI in RTM, we aggreed to show TFMs for top level packages in the properties grid separated by ';'
Bugs this fixes:
related to #587
Workarounds, if any
N/A
Risk
Low
Performance impact
none