Azure-functions-vs-build-sdk: System.Memory not found

[TclasenITVT]

Trying to run my Azure Function(V2) using netcoreapp3.0, Im getting an error when using the .AsMemory() Method on a variable.

Error Message:

System.Private.CoreLib: Exception while executing function: Function1. TestSystemMemoryAzuerFunction: Could not load file or assembly 'System.Memory, Version=4.2.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. Das System kann die angegebene Datei nicht finden. System.Private.CoreLib: Could not load the specified file.

I have created a minimal Repro here

[TimPosey2]

I'm getting similar error with Microsoft.Extensions.Logging.Abstractions when upgrading to netcoreapp3.0

[jeffputz]

Yes, this library is a non-starter for 3.0, which as best I can tell is because the right build targets are not set in the SDK project. I get similar build errors from the SDK, though usually for one 3.0.0 package or another (it varies by project).

[TimPosey2]

Is this project/repo even monitored anymore?

[jeffputz]

I pinged @fabiocav the other day, and he said that some of this is contingent on the launch of Azure Functions v3, and he pointed me here: https://github.com/Azure/app-service-announcements/issues/200

But I share your frustration, especially with this library. We've got a lot invested in Functions, and Core, and because it moves quickly with official LTS moving to new versions of the frameworks, it's rough when all of the supporting stuff for Azure, Azure DevOps, lags behind. We're ready to go to Core v3, but this is holding us back (the hard Json.net dependency has been particularly gross).

[DennisInSky]

Is there any news on this issue? The problem is still exist.

[TclasenITVT]

After updating to Azure Function V3, azure function sdk 3.0.2 and netcoreapp 3.1 this error did not occure for me anymore.

I edited my rerpo repo to show that.

[lokijota]

+1 on this.

[hendrickcastro]

Is there any news on this issue? The problem is still exist.

If the problem persists, verify that you are using the correct version of Azure Functions Core Tools (v3), it happened to me that I took version 2 from nodejs that is, I had version 2 installed in nodejs and version 3 in the folder From microsoft in the path they were both but I took the first one that was the nodejs one and it kept giving me the error until I delete the nodejs one, you can update it to version 3 in nodejs and I suppose it will work the same.