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

Build error on Visual Studio 16.1.0 #166

Closed
YZahringer opened this issue May 22, 2019 · 11 comments
Closed

Build error on Visual Studio 16.1.0 #166

YZahringer opened this issue May 22, 2019 · 11 comments

Comments

@YZahringer
Copy link

I have several compilation errors after updating Visual Studio to version 16.1.0. I use MSBuild.Sdk.Extras/2.0.24.

NETSDK1005 Assets file 'Project.Shared\obj\project.assets.json' doesn't have a target for 'UAP,Version=v10.0.16299'. Ensure that restore has run and that you have included 'uap10.0.16299' in the TargetFrameworks for your project. C:\Program Files\dotnet\sdk\2.2.204\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.target

@clairernovotny
Copy link
Collaborator

That's a bug in 16.1: dotnet/project-system#4854

@MSiccDev
Copy link

Any ideas to work around this until it gets fixed?

@glennawatson
Copy link
Contributor

According to the bug you can side-by-side install previous versions of visual studio 16. See Oren's link above for details. I wouldn't be surprised if the fix is out this week though.

@clairernovotny
Copy link
Collaborator

Closing as external. The fix will be in VS 2019 16.1.2.

@SimonCropp
Copy link

@onovotny did u forget to close?

@clairernovotny
Copy link
Collaborator

Was waiting for 16.1.2 to be released first

@SimonCropp
Copy link

@onovotny ok good plan :)

@clairernovotny
Copy link
Collaborator

@jamesmcroft
Copy link

Interestingly this issue has cropped back up again so it seems. Package version is 2.0.54 and .NET Core SDK is 3.1.201

@jalbertSyncroTech
Copy link

We're also seeing this with the latest VS 16.5.4. I've added a comment to the original dotnet bug report.

@jalbertSyncroTech
Copy link

This seems to be the same issue as #200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants