Closed yowl closed 5 years ago
I note that changing the UWP head proj: from
<Version>6.1.7</Version>
to
<Version>6.2.3</Version>
Allows for successful loading of the type.
That could be an issue caused by the fact that NuGet package references are not transitive between legacy style projects and sdk-styled projects. As of release 1.6.65, MSBuildExtras provides version 6.2.2 but the head project uses another.
There was probably a breaking change between version 6.2.2 and 6.1.7 of the Microsoft.NETCore.UniversalWindowsPlatform package
.
In a non-project dependency (e.g. if you library was referenced as a nuget package) this would not happen as the reference would be matching the one from the nuget package.
I'll adjust the Uno templates so the default works, at least.
Makes sense. If you're updating the templates you might want to change the MSBuild version from 14 to 15, unless of course you are supporting VS2015.
Solution template still has reference to this issue https://github.com/unoplatform/uno/blob/8cff819daaa72bbe694a06ffdc21424aa186d8f4/src/SolutionTemplate/UnoSolutionTemplate/UWP/UnoQuickStart.Uwp.csproj#L9 Is it still relevant?
I'm submitting a...
Current behavior
The referenced type that should be resolved through a TypeForwardTo seems to cause problems.
Expected behavior
Should be possible to reference these types from a library project.
Minimal reproduction of the problem with instructions
Take the repo at https://github.com/yowl/UnoStandardRefTest build, deploy and run the UWP head, and hopefully it will fail with
It works ok if the type is used in the UWP head directly.
Environment