Support for 64bit function development

[paulbatum]

You can configure your function app to run in 64 bit mode when running in Azure, but the local experience in visual studio does not support running locally in 64 bit. If you try to switch your project over to target x64 you'll get the following error:

Could not load file or assembly 'file:///C:\Users\pbatum\Source\Repos\FunctionApp3\bin\x64\Debug\net461\FunctionApp3.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format

[ahmelsayed]

ref: Azure/azure-functions-core-tools#117

[simeyla]

@paulbatum But this still doesn't give me 64 bit Node right?
I'm primarily using .NET Core but I have one Node service I need (sharp) that requires 64 bit Node to run.

Anybody know if there will be upcoming support for this ?

[paulbatum]

So functions inherits the behavior of App Service and I just investigated and it looks like App Service does not provide x64 node.exe built in.

It might be possible to workaround this by uploading your own x64 version of node and then using the app setting languageWorkers:node:defaultExecutablePath to point at that version. But I haven't tried this.

[Kjue]

I can verify that this approach works. I've just done it as I have custom modules that require them to run on 64-bit architecture. You just go to the app settings and enter the local path for the node executable you want to be running. This of course is a way of defining your node environment at the same time too. Thanks for the help @paulbatum!

I downloaded the related NodeJS release zip from the node repository at https://nodejs.org/download/release/ and uploaded the unzipped package as part of my deployment to the function. Then I set the variables like this:

languageWorkers:node:defaultExecutablePath : D:\home\site\wwwroot\node-v8.12.0-win-x64\node.exe

[Frankwayne]

Thanks @Kjue @paulbatum updating the node js.exe to a 64 solved my out of memory problems.

I'm unsure if thjis is needed but I also updated the application setting "general setting: platform" from 32 bit to 64 bit as well.

[Frankwayne]

I forgot to mention as well. If you are using the run from zip setting, be sure to place your node.js exe in a different place than wwwRoot. I did mine one level above wwwRoot in a folder called D:\home\site\wwwroot\NodeV8.12.0x64 \node.exe

[Kjue]

Yes, it is necessary to upgrade the environment to 64bit to run node in that. I should then also add that I deployed with Visual Studio Code. Just had the node folder as part of the main folder for functions. Cheers!

[Frankwayne]

if you wish to debug in visual studio with the 64 bit azure functions runtime you can peform the steps I have outlined in this issue

Azure/azure-functions-core-tools#117

Be warned though you are pretty much fooling the Azure functions and web jobs tools extensions into running your version of the Azure functions CLI

[paulbatum]

@Frankwayne Just FYI, I outlined a somewhat less invasive approach in my comment here. This has the added benefit of letting you switch easily between the built in bits and the 64bit build.

[Frankwayne]

very nice. I will have to share this with my team. I think this will be the preferred method of updating the azure functions core tooling.

[ColbyTresness]

This issue was moved to Azure/azure-functions-vs-build-sdk#291

[ColbyTresness]

Reverting move, tracking here.

[ColbyTresness]

@soninaren what are your thoughts on this one?

[soninaren]

@ColbyTresness We already provide a 64 bit version of CLI to VS. The pending work here is on the VS team to use that when the user selects x64 from the drop down in VS.
https://github.com/Azure/azure-functions-tooling-feed/blob/master/cli-feed-v3.json#L1708

[ColbyTresness]

@vijayrkn are you tracking this?

[vijayrkn]

I will add an item to our backlog to track this.

[AngelosP]

Visual Studio 2019 16.4 P1 has added support for this :)

[ColbyTresness]

Closing per above!

[mahesh2000]

is there a way to run 64-bit node.exe for azure functions on the server? i'm unable to run the sharp module (it's for svg to png image conversion) as it requires this. thanks!

[soninaren]

cc: @mhoeger

[kevinclarkadstech]

Ugh I wasted a bunch of time trying to deploy an Azure function to face this same issue.

[mhoeger]

Hi @kevinclarkadstech - sorry about that ! Please see here for the latest guidance: Azure/azure-functions-nodejs-worker#158 (comment) .

You should just be able to switch the app's configuration to "64-bit" and it should work without having to add the app setting Paul described.