.NET 10

[tivanchuk-hawe]

Is your feature request related to a problem? Please describe.
.NET 8 EoL

Describe the solution you'd like
Since PnP.Core & PnP.Framework already have .NET 10 versions, would be nice also to have one for PnP.PowerShell for PowerShell 7.6

Describe alternatives you've considered
nope

Additional context
.NET EoL 10. Nov. 2026

[gautamdsheth]

hey @tivanchuk-hawe , this is planned towards the end of the year. We are still on .NET 8 as we need to support PowerShell 7.4, once that is out of support around Nov, we will update this.

[tivanchuk-hawe]

@gautamdsheth from security perspective - I have to run outdated .NET/PS for couple of months after .NET 8 EoL to make an actual upgrade everywhere, so would be nice to have this update before the actual EoL, so I (and the rest of communiy) have a time to update everything w/o using outdated .NET/PS...

[tivanchuk-hawe]

@gautamdsheth recently function core tools internally migrated to some v10 libraries, so now essentially PnP.Framework doesn't work in PowerShell v7.4 Azure Function due to dlls clash. v3.3.0 already using Core & Framework which both have .NET 10 targets, so I just wondering - what stops PnP.PowerShell from multitargeting also for .NET 10?

This will allow to use PnP.PowerShell with PS 7.6 Azure Functions and give people time to safely migrate before .NET 8 /PS 7.4 EoL

[gautamdsheth]

@tivanchuk-hawe - the issue related to Azure functions has been fixed in the latest nightly builds, check this issue.

#5350

We used to do multitargeting but it had a lot of subtle runtime bugs, conditional code blocks and hard to debug issues which we want to avoid. That's why we decided to remove that.
We might revisit this but for now our baseline will be .NET 8/ PS 7.4 , in November once .NET 8 is EOL , we will be do a major release 4.0 which will be based on .NET 10.

[tivanchuk-hawe]

@gautamdsheth thx, issue with Azure Function is now resolved.

What I don't understand - why wait for EoL, I don't think anyone, security aware, would actually wait for EoL to move to .NET 10/PS 7.6. Normally, you would like to move in advance, to stay always on supported and patched version. So why not to switch e.q. in September - giving developers smth like 1-2 months to move all apps before EoL?

[gautamdsheth]

That’s a valid point, and in many cases moving early makes sense.

In our case, because PnP PowerShell is super widely used in different surfaces such as Azure functions, automation, AWS etc., upgrading the runtime is a breaking change. As long as .NET 8 is supported, we prefer to keep stability for users and align with the official lifecycle rather than forcing an earlier transition. We have limited time and capacity for all these changes.

We will of course communicate and plan the move ahead of EoL to give everyone enough time to prepare.