Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Preview 2 regression: UWP target not restoring

See original GitHub issue

Moved from https://github.com/dotnet/cli/issues/6829

Steps to reproduce

Try to build in VS 2017 15.3 with preview2 and today’s nightly .NET Core 2 tooling:

Clone https://github.com/Reactive-Extensions/Rx.NET checkout develop Open Rx.NET/Source/System.Reactive.sln

This worked with the .NET Core 2 preview 1 tooling.

Expected behavior

Restore and build should work

Actual behavior

Severity	Code	Description	Project	File	Line	Suppression State
Error		Assets file 'C:\dev\RxNET\Rx.NET\Source\src\System.Reactive\obj\project.assets.json' doesn't have a target for '.NETCore,Version=v5.0'. Ensure you have included 'netcore50' in the TargetFrameworks for your project.	System.Reactive	C:\Program Files\dotnet\sdk\2.0.0-preview2-006391\Sdks\Microsoft.NET.Sdk\build\Microsoft.PackageDependencyResolution.targets	164

Environment data

dotnet --info output:

.NET Command Line Tools (2.0.0-preview2-006391)

Product Information:
 Version:            2.0.0-preview2-006391
 Commit SHA-1 hash:  ef5d4b47c3

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.16215
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0-preview2-006391\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview2-25407-01
  Build    : 40c565230930ead58a50719c0ec799df77bddee9

Issue Analytics

State:
Created 6 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

3reactions

srivatsncommented, Jun 16, 2017

You can add a NoWarn to the PackageRef now like this:

<PackageReference Include="Nustache" Version="1.16.0.4" NoWarn="NU1701" />

1reaction

nguerreracommented, Jun 16, 2017

That is expected and something that was designed to happen as part of the move to AssetTargetFallback. It is telling you something true: the .NETFramework library pulled in by the .NETCoreApp project might not actually work at runtime on .NET Core.

There’s a way to suppress this on the individual package reference, but I’m having trouble locating the syntax. @rrelyea, @emgarten, @terrajobst Are there docs for this that we can point folks to?

Top Results From Across the Web

Preview 2 regression: UWP target not restoring · Issue #8369

Steps to reproduce Try to build in VS 2017 15.3 with preview2 and today's nightly .NET Core 2 tooling: Clone https://github.com/Reactive-Extensions/Rx.NET ...

Preview channel release notes for the Windows App SDK

Both regressions will be restored in the next stable release. Version 1.1 Preview 2 (1.1.0-preview2). This is the second release of the preview ......

`HasSharedItems` is explicitly set to empty by VS causing ` ...

In VS 2022 17.1 Preview 3, the HasSharedItems property is set to empty string as an global value (making the HasSharedItems value set...

Infinite suggested action never ends. - Developer Community

Hi basspits basspits,. A fix for this is available in 16.9 Preview 2 and newer. I would not recommend making changes to the...

msbuild - *.targets cannot be imported again. It was already ...

I have UWP app build in VS 2017 and many project in my solution have build warning like below. How to get rid...