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.
UAP target doesn't have package references properly generated/used
See original GitHub issueWhen trying to cross compile with a project that includes a uap10.0 target, the csc task doesn’t have the package references resolved correctly and put on the CSC task.
To repro, look at the vs2017 branch of https://github.com/onovotny/Zeroconf/tree/vs2017
In there you’ll see it cross-compiling to netstandard1.3 and uap10.0. The problem is that it’s using the wrong mscorlib reference for uap10.0 and when you look at the msbuild log and csc task invocation, it’s not passing the correct /reference’s that include all of the package dependencies that come from both the NETStandard.Library and the Microsoft.NETCore.UniversalWindowsPlatform reference. The RAR task seems to not generate anything.
Not sure if this is in the SDK tasks or the NuGet tasks?
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@nguerrera adding that line to disable the local lock file copy did the trick. The LanguageTargets did not.
maybe?