I want to my azure function from v1 to v4 my current dotnet framework is 4.8 need suggestion which version should I go 4.8 or 8 or 9
I want to my azure function from v1 to v4 my current dotnet framework is 4.8 need suggestion which version should I go 4.8 or 8 or 9.
I am try to migrate to 4.8 with v4 but as per microsoft guide it mentioed to add output type as exe and mine was class library getting multiple error.
Any upgrade assistant for 4.8 with v4
I find upgrade assistant for .net 8
Azure Functions
-
Sai Prabhu Naveen Parimi • 1,255 Reputation points • Microsoft External Staff
2025-04-22T07:48:17.6966667+00:00 Thanks for your question regarding the migration of your Azure Function from version 1 to version 4.
You're correct — when targeting .NET Framework 4.8 with Azure Functions v4 (using the in-process model), Microsoft requires changing the output type to
Exe
. This change can cause issues if your current project is structured as a class library, as it’s not designed for that output format. These compatibility issues are common in this scenario.To clarify your follow-up question:
Is there an Upgrade Assistant for 4.8 with v4? No — the .NET Upgrade Assistant is not designed to assist with migrating to .NET Framework 4.8. Instead, it helps migrate projects from .NET Framework (like 4.8) to modern .NET versions such as .NET 6, 7, or 8.
For this reason, recommend migrating your Function App to .NET 8 using the isolated worker model, which:
- Allows you to keep your class library structure (no need to change to
Exe
) - Offers long-term support through November 2026
- Avoids the limitations and legacy constraints of .NET Framework-based deployments
You can use the .NET Upgrade Assistant to help with this transition.
Helpful resources:
- Allows you to keep your class library structure (no need to change to
-
Rashmiramchandra Prabhu • 66 Reputation points
2025-04-22T08:45:54.36+00:00 You mentioned .net 8 is long term support but my v1 is supporting till september 2026 so its like only 2 month extended support but what after that .Should I need to migrate it again to some other version?
-
Sai Prabhu Naveen Parimi • 1,255 Reputation points • Microsoft External Staff
2025-04-23T06:34:18.39+00:00 Thank you for your question. To provide clarity on the Azure Functions support timelines:
- Your current application is running on Azure Functions v1, which is supported until September 2026.
- If you migrate to .NET 8 (LTS) with Functions v4, the .NET 8 runtime will be EOF life by November 2026 which means functions running on this runtime will continue to run but it reaches of end of support.
So even though .NET 8 and Functions v1 may both reach end-of-life around late 2026, once you're on v4 with isolated .NET, you'll be in a much better position to upgrade to future versions like .NET 10 LTS with minimal changes.
Please let me know if this answers your question.
-
Sai Prabhu Naveen Parimi • 1,255 Reputation points • Microsoft External Staff
2025-04-24T08:08:00.97+00:00 Just checking to see if the above information helped clarify your query. Let me know if you have any further questions.
-
Sai Prabhu Naveen Parimi • 1,255 Reputation points • Microsoft External Staff
2025-04-25T05:52:47.1033333+00:00 Following up to see if you had a chance to review the information shared earlier. Please let me know if you have any questions or need further clarification.
-
Rashmiramchandra Prabhu • 66 Reputation points
2025-04-25T11:35:41.31+00:00 I have installed visual studio 2022 and .net 8 and then upgrade assistant but upgrade not successful giving 108 errors .I also changed the nuget packages with the latest version .Can you please suggest any help here
-
Sai Prabhu Naveen Parimi • 1,255 Reputation points • Microsoft External Staff
2025-04-28T08:11:34.08+00:00 To better assist you with your migration issues, could you please help clarify the following points:
What specific errors are you encountering during the upgrade process?
Are there any third-party libraries or dependencies in use that may only be compatible with .NET Framework 4.8?
Which process model are you currently using for your Azure Functions (in-process or isolated)?
Have you confirmed that your Visual Studio setup and project templates are fully updated?
These details will help us provide more targeted guidance for your migration scenario.
For your reference, here are some helpful documents:
-
Rashmiramchandra Prabhu • 66 Reputation points
2025-04-28T11:01:57.6633333+00:00 1)I am trying to fix error still some error with namespaces like using Microsoft.ServiceBus.Messaging; or using Microsoft.ApplicationInsights;using Microsoft.ApplicationInsights.Extensibility;
2)public static async Task<IActionResult> Run([HttpTrigger(AuthorizationLevel.Function, "post", Route = null)] HttpRequest req)
{
try { string ediFF = await req.Content.ReadAsStringAsync();
here getting error 'HttpRequest' does not contain a definition for 'Content' and no accessible extension method 'Content' accepting a first argument of type 'HttpRequest' could be found (are you missing a using directive or an assembly reference?)
- var request = new RestRequest("oauth2/token", DataFormat.Json);
Argument 2: cannot convert from 'RestSharp.DataFormat' to 'RestSharp.Method'
-
Sai Prabhu Naveen Parimi • 1,255 Reputation points • Microsoft External Staff
2025-04-29T07:33:10.7666667+00:00 Thanks for sharing the update on your Azure Functions migration. Based on the issues you're facing, here are a few steps that should help you move forward:
1. Namespace Compatibility
Replace
Microsoft.ServiceBus.Messaging
with the updatedAzure.Messaging.ServiceBus
SDK, which is the modern and recommended package for Azure Service Bus.For Application Insights, if you're using the isolated worker model in .NET 8, use the
Microsoft.ApplicationInsights.WorkerService
package. If you're using in-process with ASP.NET Core, you can useMicrosoft.ApplicationInsights.AspNetCore
.2. Reading Request Body
If you're seeing an error like
'HttpRequest' does not contain a definition for 'Content'
, and you're targeting .NET 8 with the isolated worker model, update your method to useHttpRequestData
and read the body as follows:string ediFF = await new StreamReader(req.Body).ReadToEndAsync();
Refer to the official guidance on isolated worker model for implementation patterns.
3. RestSharp API Update
Recent versions of RestSharp (v107+) introduced breaking changes. If you're getting parameter conversion errors, update your code like this:
var request = new RestRequest("oauth2/token", Method.Post);
Make sure you refer to the RestSharp migration guide for any updated syntax and method usage.
-
Rashmiramchandra Prabhu • 66 Reputation points
2025-05-02T11:06:09.2633333+00:00 I changed my project and number of error reduced still getting error for azure storage it is requiring namespace using Microsoft.WindowsAzure.Storage;using Microsoft.WindowsAzure.Storage.Blob;
still getting error in listblob as no such method
CloudStorageAccount storageAccount = CloudStorageAccount.Parse(connstr);
CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();
var container = blobClient.GetContainerReference(prefix);
var x=container.ListBlobsSegmentedAsync()
var blobs = container.ListBlobs(prefix: null, useFlatBlobListing: true);
DateTime UTCDatetime = DateTime.UtcNow;
foreach (CloudBlockBlob blob in blobs)
Sign in to comment