-
Notifications
You must be signed in to change notification settings - Fork 199
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
Support for dot net core based functions that target x64 #651
Comments
Thanks @Oceanswave - let me see what all is involved here and make sure we are tracking in the right repo. / cc @fabiocav @paulbatum to help with triage / milestones |
Thanks for the eyes, @jeffhollan, let me know if I can help. |
Hi, BTW:
Thanks! |
We are in the process of deploying a release that has a fix for this issue. I expect the release will be deployed globally by 8/3. If you want to try it out early, create a function app in West Central US and use that for your testing. If you're having problems, first verify that you're getting 11946 or newer: The platform switcher is here: The following HTTP triggered C# function will demonstrate: using System.Net;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Primitives;
public static IActionResult Run(HttpRequest req, TraceWriter log)
{
var is64bit = Environment.Is64BitProcess;
log.Info($"Is x64: {is64bit}");
return new OkObjectResult(is64bit ? "x64" : "x86");
} |
@paulbatum @fabiocav - are there any instructions for getting x64 Azure Functions running locally in VS during |
Hello, see this comment and the associated linked resource: That should be enough to unblock you (if not being exact step by step instructions). |
For further questions about x64 in local development scenarios, see #376 |
In the current Azure Functions preview, it's possible to create functions that target x64, including dotnet core based functions.
However, when attempting to deploy a x64-based function to Azure, the Azure Functions runtime invokes the x86-based dotnet executable, regardless of the platform architecture specified for the app service.
The text was updated successfully, but these errors were encountered: