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
[UWP] F# code usage fails Azure DevOps build #54765
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Hi @xperiandri, thanks for posting this issue. .NET Native ships as a Nuget package. It seems that the AzDO script assumed it was restored to the local nuget package folder. As a performance optimization VS ships the latest .NET native package in the off-line nuget cache. This enables the project creation scenario with File->New C# UWP without needing to download the .NET native toolchain. Unfortunately Program Files is read-only, and unless the script has write access to that folder, it will not be able to update the gatekeeper xml. As I am sure you aware, F# is not an officially supported scenario hence it is disabled by default. |
So what is next? What does closing this issue mean? |
.NET native does not officially support F# scenarios |
According to dotnet/corert#6055 UWP apps referencing F# library must build.
But they are not.
Unless I execute
build fails.
But this hack works only for
Microsoft.NETCore.UniversalWindowsPlatform
with version less than current, i.e. less than 6.2.12And for current it fails
Because I have not write access to
C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.net.native.compiler\
The text was updated successfully, but these errors were encountered: