FS#59274 - [dotnet-sdk] .NET Core SDK throws warnings compiling Azure Functions

Attached to Project: Community Packages
Opened by Veli-Jussi Raitila (vjraitila) - Sunday, 08 July 2018, 20:24 GMT
Last edited by Maxime Gauduin (Alucryd) - Thursday, 20 September 2018, 17:36 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Running 'dotnet build' on Azure Functions project throws warnings on Arch. This does not happen on Fedora 28, nor on Windows

Additional info:
* dotnet-sdk 2.1.1+301-1

STEP TO REPRODUCE

1. Clone https://github.com/vjraitila/archbugs-dotnet-functions
2. run 'dotnet build'

EXPECTED RESULTS
- Clean build with 0 warnings and 0 errors

ACTUAL RESULTS
- 2 build warnings - warning NU1603: Arch.Bugs.FsharpCoreFunctions depends on NETStandard.Library (>= 2.0.2-servicing-26420-0) but NETStandard.Library 2.0.2-servicing-26420-0 was not found. An approximate best match of NETStandard.Library 2.0.2 was resolved.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Thursday, 20 September 2018, 17:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  builds without warning with 2.1.4
Comment by Veli-Jussi Raitila (vjraitila) - Sunday, 08 July 2018, 20:49 GMT
Running 'dotnet --info' shows that SDK versions match in all environments. However, the build engine is of a different version.

Fedora 28 and Windows 7 show:

Microsoft (R) Build Engine version 15.7.179.6572 for .NET Core

Arch Linux shows:

Microsoft (R) Build Engine version 15.7.179.62826 for .NET Core
Comment by Veli-Jussi Raitila (vjraitila) - Monday, 09 July 2018, 06:47 GMT
Compiles cleanly on macOS 10.13.5 as well:

Microsoft (R) Build Engine version 15.7.179.6572 for .NET Core
Comment by Thiago França (tfsthiagobr98) - Friday, 20 July 2018, 21:58 GMT
I can confirm when build show Error : depends on NETStandard.Library (>= 2.0.2-servicing-26420-0) but NETStandard.Library 2.0.2-servicing-26420-0 was not found. An approximate best match of NETStandard.Library 2.0.2 was resolved.
Comment by Pete Anderson (P_Daddy) - Tuesday, 31 July 2018, 12:26 GMT
This reproduces for me on any .NET Core project:

% mkdir TestCore
% cd TestCore
% dotnet new classlib
...
% dotnet restore
/home/pete/code/TestCore/TestCore.csproj : warning NU1603: TestCore depends on NETStandard.Library (>= 2.0.2-servicing-26420-0) but NETStandard.Library 2.0.2-servicing-26420-0 wa
s not found. An approximate best match of NETStandard.Library 2.0.2 was resolved.
Restore completed in 57.98 ms for /home/pete/code/TestCore/TestCore.csproj.
%
Comment by Pete Anderson (P_Daddy) - Tuesday, 31 July 2018, 12:40 GMT
Workaround: downgrade from dotnet-sdk-2.1.2+302-1 to dotnet-sdk-2.1.300-1.
Comment by Veli-Jussi Raitila (vjraitila) - Wednesday, 01 August 2018, 07:38 GMT
The package has multiple unresolved issues. If you do not need a global installation, instead of downgrading, I think the best workaround is to just unpack the SDK from the official Microsoft tarball into your home directory and use the tools from there. Add the 'dotnet' executable into your PATH and everything works. Even the NuGet package cache will be appropriately populated upon first start, which is something this PKGBUILD does not do either.

Loading...