"One or more projects are not UAP compliant, Version = v10.0" [UWP] problem
I am developing a UWP app until I got this error (picture below). I searched for a solution but couldn't find anything. It doesn't even say which package is incompatible. How can I find the incompatible package in my solution? Also is there a way to recreate project.json automatically? I am asking this because I changed something to project.json and broke it more.
Also I am using VS2017 and I can run the project without any problem. I just can't update the package.
Thank.
(github link for the project if you want to look at it.)
source to share
I used your GitHub project https://github.com/almorax/dota2-handbook-uwp to fix the problem and it looks like the problem is related to how the nuget package is being pushed to the "Dota2Handbook" Project. In other projects, you have used the PackageReference method to refer to the nuget package, but in the Dota2Handbook project, you use project.json to refer to the nuget package. When I changed the "Dota2Handbook" project to use the "PackageReference" method, I was able to get the latest package.
Note. You will notice that the Dota2Handbook.Infrastructure project is already using the new way to submit Nuget packages
More on PackageReference: https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files
source to share
What happened to me is that I have UWP projects that were made on VS 2015 and initially target RTM for Windows 10. These projects have been updated to VS 2017 and are aimed at updating the Creator. Everything worked fine and all projects still used the original style project.json
.
Then I tried to create a new Windows Runtime Component and configure the Target Creator Update initially. The Targeting Creator update in VS 2017 forces the project to use the new project style PackageReferences
. This caused the errors mentioned in the above question when I was referencing a WinRT component from a UWP app.
Instead of converting all of my old UWP project files to the new format, I target the new UWP or WinRT Content Center on the Anniversary Edition (which uses the old project style project.json
) and then migrate to the Creator Update.
Of course, it might be appropriate to update the project file at some point, just be aware that it will no longer be supported by VS 2015. Conversion steps are shown here.
source to share