Queries on migration of function apps

salilsingh-9961 346 Reputation points
2024-04-01T15:40:10.2533333+00:00

Hi Team,

I am working on migrating my Azure Function apps from .net 6 to .net 8. Requesting to please help with below points -

  1. .Net version that a function app uses is present in <TargetFramework></TargetFramework> of csproj file, can you pls confirm.
  2. Currently there is no support for in-progress function app in .net 8, it is expected to come soon (well before the .net 6 expiry date for function app), please confirm.
  3. What is the criteria on which we could decide that an in-progress function app has to move to isolated worked process?
  4. Is there any scenario due to which an in-progress function app cant be migrated to isolated worker process OR all in-progress function apps could be migrated to isolated worker process?
  5. I am unable to see .net runtime used in my function app, what could be the reason?
  6. While migrating function apps from .net 6 to 8, how to pass the value of logger?
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,200 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Marcin Policht 8,415 Reputation points MVP
    2024-04-01T16:34:27.98+00:00
    1. Yes, the .NET version that a function app uses is present in the <TargetFramework></TargetFramework> tag of the csproj file.
    2. As of now, there is no official support for .NET 8 in Azure Functions. However, Microsoft is working on adding support for .NET 8 to Azure Functions. They have not yet announced a release date, but it is expected to be available before the .NET 6 expiry date for function apps.
    3. The decision to move an in-progress function app to an isolated worker process depends on the specific needs of the app. Generally, if your app requires more control over the runtime environment or needs to run in a more secure environment, it should be moved to an isolated worker process.
    4. There may be certain scenarios due to which an in-progress function app can't be migrated to an isolated worker process. For example, if the app relies on certain Azure Functions features that are not supported in the isolated worker process, you may not be able to migrate it. However, in most cases, all in-progress function apps can be migrated to an isolated worker process.
    5. If you are unable to see the .NET runtime used in your function app, it could be because your app is using the default runtime provided by Azure Functions, which is currently .NET 6. However, if you have explicitly set the .NET runtime version in your function app configuration, you should be able to see it.
    6. To pass the value of the logger while migrating function apps from .NET 6 to 8, you can use the ILogger interface provided by .NET. You can inject the ILogger instance into your functions and use it to log messages. The ILogger interface has methods for logging messages at different levels, such as Debug, Information, Warning, and Error.

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    1 person found this answer helpful.
    0 comments No comments