Azure Functions Script (.csx) support for .NET 6

What problem would the feature you’re requesting solve? Please describe.

Any attempt I’ve made to target a framework other than netstandard2.0 in Azure Scripts yields cryptic warnings and errors when referencing Nuget packages, as detailed in this StackOverflow post.

Describe the solution you’d like

• If frameworks outside of netstandard2.0 are not supported, the runtime should clearly indicate that with an error when the function.proj file sets an unsupported target.
• If frameworks outside of netstandard2.0 are supported, then I need help understanding why I’m getting the errors I’m seeing, and what steps are required to get, say, .NET 6, working.
• In either case, the documentation should be updated. (Do I need to file a separate issue here for that?

Describe alternatives you’ve considered

Lack of modern framework support makes me think I should be using Azure Function C# Libraries instead. Again, the documentation should make this limitation clear so developers don’t go down the csx road a ways before realizing it’s a dead-end.

Additional context

I’ve been getting the general impression that Azure Functions Scripts is a forgotten/stale technology. I’m frequently finding suggestions about how to do things like leverage IHttpClientFactory in Azure Functions (to avoid socket starvation and stale DNS problems), and how to leverage dependency injection in Azure Functions, only to discover that none of it works in Azure Functions Scripts. I’m wondering if I should recommend that our teams not bother with Scripts, even for relatively simple scripts.

[v-bbalaiagar]

Hi @j2jensen , Apologies for the confusion, I have updated the issue link in the above comment. We shall keep the issue open and will investigate this further and update you with the findings.

[chinazor-allen]

Following. Would be nice to know the workaround for csx files using .NET 6.