You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of .NET does your existing project use?
.NET 6
What version of .NET are you attempting to target?
.NET 8
Description
If I build an Azure Function with the In-Process model, on .NET 6, I am able to run it on .NET 8 Isolated in Azure.
I don't understand why this works, I thought the Isolated-Worker would not accept existing In-Process Functions?
Can someone explain why this works? I can't find any source or reference which states that this should work.
Steps:
Have an existing Azure Function on Azure
Create an empty Azure Function, In-Process, .NET 6.0, Http Trigger in Visual Studio
run dotnet publish -o Publish
Zip deploy using Azure CLIaz functionapp deployment source config-zip
Make sure the Azure Function App Configuration has FUNCTIONS_WORKER_RUNTIME with value dotnet-isolated. If not, change it.
Project configuration and dependencies
Empty .NET 6 In-Process Azure Function Project with HttpTrigger
Chrissie
changed the title
Question: .NET 6 In-Proceses function runs fine on Azure .NET 8 Isolated ?!
Question: .NET 6 In-Process Function runs fine on Azure .NET 8 Isolated ?!
Aug 22, 2024
What version of .NET does your existing project use?
.NET 6
What version of .NET are you attempting to target?
.NET 8
Description
If I build an Azure Function with the In-Process model, on .NET 6, I am able to run it on .NET 8 Isolated in Azure.
I don't understand why this works, I thought the Isolated-Worker would not accept existing In-Process Functions?
Can someone explain why this works? I can't find any source or reference which states that this should work.
Steps:
dotnet publish -o Publish
az functionapp deployment source config-zip
FUNCTIONS_WORKER_RUNTIME
with valuedotnet-isolated
. If not, change it.Project configuration and dependencies
Link to a repository that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: