netFrameworkVersion in Azure App Services Api App

Question

I'm configuring a api app in azure with bicep. This is a dotnet core 3.1 app. For netFrameworkVersion i provide 'v3.1', this however doesn't work. The deployment of the Bicep template does work, but my application does not. The value of .NET version is empty in the portal.

When i manually change the version in the portal, and do an export of my app, the returned ARM template is sets netFrameworkVersion to 'v4.0'. I am very confused, what is happening here? I can't seem to find any documentation about this.

Thomas · Accepted Answer · 2023-04-18T06:36:10.973

8

You need to specify the CURRENT_STACK metadata and the netFrameworkVersion property inside the siteConfig section:

resource webapp 'Microsoft.Web/sites@2018-11-01' = {
  ...
  properties: {
    ...
    siteConfig: {
      ...
      netFrameworkVersion: 'v6.0'
      metadata: [
        {
          name: 'CURRENT_STACK'
          value: 'dotnet'
        }
      ]
      ...
    }
    ...
  }
}

edited Apr 18 '23 at 06:36

answered Feb 14 '22 at 16:10

Thomas

24,234
6
81
125

Hi, thx for your help. Do you know where i can find documentation about this metadata parameters? there does not seem to be any on the official web/sites docs https://learn.microsoft.com/en-us/azure/templates/microsoft.web/2018-11-01/sites?tabs=bicep . – Amateur Feb 14 '22 at 16:23
Doesnt seems to be well documented but this sample from MS doc use that: https://learn.microsoft.com/en-us/azure/azure-monitor/app/resource-manager-web-app – Thomas Feb 14 '22 at 16:46
1

Observation: for .NET 6, the ARM template generated by Azure Portal has `CURRENT_STACK=dotnet`, and no longer `CURRENT_STACK=dotnetcore`, so I guess that would be the correct value for modern .NET versions. – Paweł Bulwan Sep 29 '22 at 11:14

Bob Bracke · Answer 2 · 2022-11-23T10:59:49.953

0

Microsoft changed this with newer API versions, it now uses the property "linuxFxVersion" to set this:

resource webapp 'Microsoft.Web/sites@2020-12-01' = {
...
   properties: {
     ...
     siteConfig: {
        ...
        linuxFxVersion: 'DOTNETCORE|6.0'
     }
   }
}

edited Nov 23 '22 at 10:59

answered Nov 23 '22 at 10:59

Bob Bracke

1
1

score 0 · Answer 3 · answered Nov 30 '22 at 04:28

0

For me I had to set the netFrameworkVersion in the siteConfig section:

resource functionapp 'Microsoft.Web/sites@2022-03-01' = {
...
   properties: {
     ...
     siteConfig: {
        ...
        netFrameworkVersion: '6.0'
     }
   }
}

answered Nov 30 '22 at 04:28

Mr-DC

799
5
14
25

Is it 6.0, or v6.0? – Palec Feb 03 '23 at 01:45
1

@Palec Just 6.0 exactly as I have it above – Mr-DC Feb 03 '23 at 12:02
Have seen the other variant in many places. Will try once I upgrade the code of the App Service I am maintaining. – Palec Feb 03 '23 at 12:19

score 0 · Answer 4 · answered Apr 21 '23 at 10:26

As of 21 April 2023 the following worked for me. metadata within siteConfig was displayed as invalid, but adding metadata as a separate config resource worked:

resource webApplication 'Microsoft.Web/sites@2022-03-01' = {
  name: 'my-app-name'
  ...
  properties: {
    ...
    siteConfig: {
      netFrameworkVersion: 'v6.0'
    }
  }
  resource meta 'config@2022-03-01' = {
    name: 'metadata'
    kind: 'string'
    properties: {
      CURRENT_STACK: 'dotnet'
    }
  }
}

netFrameworkVersion in Azure App Services Api App

4 Answers4