dotnet / dotnet/project-system

P2P refs choose first tfm in multi-targting reference, not closest one in legacy project system

Open
#1,162 37 comments 12 reactions 1 assignee Claimed by @davkean View on GitHub
Feature-Multi-Targeting Legacy Triage-Approved
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

_From @onovotny on December 19, 2016 20:52_

In my solution, I have a multi-targeting project creating the following outputs: `netstandard1.2;netstandard1.3;net45;win81;wpa81;MonoAndroid70;Xamarin.iOS10`

When I do a P2P reference from an iOS app, a NET 4.5 unit test project, etc, they all pick `netstandard1.2` as shown on the properties path of the reference:
![ref](https://cloud.githubusercontent.com/assets/1427284/21328651/047d1b2a-c603-11e6-90bf-6fb63aa627dd.png)

You can repro this by loading the following https://github.com/onovotny/microsoft-authentication-library-for-dotnet/commit/d41e237f3fd1f9b6da06064b6d31046b9c19fbd2.

Build src\Microsoft.Identity.Client and then look at the properties of the test project below (and of the other sample projects.

_Copied from original issue: dotnet/sdk#535_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.