{"action":"opened","issue":{"url":"https://api.github.com/repos/dotnet/sdk/issues/1408","repository_url":"https://api.github.com/repos/dotnet/sdk","labels_url":"https://api.github.com/repos/dotnet/sdk/issues/1408/labels{/name}","comments_url":"https://api.github.com/repos/dotnet/sdk/issues/1408/comments","events_url":"https://api.github.com/repos/dotnet/sdk/issues/1408/events","html_url":"https://github.com/dotnet/sdk/issues/1408","id":242750975,"number":1408,"title":"Cannot target uap10.0 apps with new TargetFrameworks syntax","user":{"login":"mqudsi","id":606923,"avatar_url":"https://avatars0.githubusercontent.com/u/606923?v=3","gravatar_id":"","url":"https://api.github.com/users/mqudsi","html_url":"https://github.com/mqudsi","followers_url":"https://api.github.com/users/mqudsi/followers","following_url":"https://api.github.com/users/mqudsi/following{/other_user}","gists_url":"https://api.github.com/users/mqudsi/gists{/gist_id}","starred_url":"https://api.github.com/users/mqudsi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mqudsi/subscriptions","organizations_url":"https://api.github.com/users/mqudsi/orgs","repos_url":"https://api.github.com/users/mqudsi/repos","events_url":"https://api.github.com/users/mqudsi/events{/privacy}","received_events_url":"https://api.github.com/users/mqudsi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-13T16:00:20Z","updated_at":"2017-07-13T16:00:20Z","closed_at":null,"body":"Forgive me if this is already formally bugged somewhere, but while I've seen lots of references to uap10 targeting issues, I didn't come across an issues that specifically addressed `<targetframeworks>` support.\r\n\r\nWhile in general the documentation for `TargetFrameworks` and the new .csproj format seems to be, shall we say, on the skimpier side; I'm unable to devise whether or not - in theory - targeting UAP10.0 should work in a multi-targeted csproj.\r\n\r\nI know UWP/UAP support is a bit of a thorn in the side of the dotnet sdk and corefx teams, but it's very unclear as to how exactly it fits in to the picture.\r\n\r\nA .NET library created with `<TargetFrameworks>netstandard1.3</TargetFrameworks>` can be consumed by a \"legacy\" UWP/UAP10 project, but there does not seem to be a way of creating a multi-targeted .NET library that includes a dependency on UWP.\r\n\r\nEither UWP is a framework target, in which case `<TargetFrameworks>uap10.0</TargetFrameworks>` should work, or UWP is a .NET Standard target w/ access to Windows-specific and platform-specific libraries (which is what is most-heavily implied in the .NET Standard documentation). However, functionally that does not seem to be the case since a .NET Standard library (`<TargetFrameworks>netstandard1.3</TargetFrameworks>`) cannot install `microsoft.netcore.universalwindowsplatform` as a dependency.\r\n\r\nWe're left in a limbo state where it seems projects targeting UAP/UWP must use the legacy csproj format, because they're neither full-fledged framework targets nor do they have .NET Standard-compliant libraries."}}
{"actor":{"display_login":"mqudsi"}}