Several questions have come in recently from customers asking about plans to remove the dependency on Microsoft’s .NET Framework 3.5 version, which will reach end of life in 2029.

We are aware of the upcoming deprecation, and keep a close eye on all of our technology dependencies to ensure we stay on current, supported versions to help our customers remain secure and stable.  

We are working to address this dependency, and it’s not a simple upgrade for the K2 server and sites. Where we can, in some of the supporting micro services, we’ve already updated our code to depend on .Net Core versions. 

I don’t have a firm release date for completely removing our dependency on .NET Framework 3.5, but when past APIs have reached EOL (for example, the Microsoft AAD API to the new Microsoft Graph API), we addressed it in all supported versions with plenty of time for customers to upgrade. And we are committed to doing that for .NET Framework 3.5’s end of life in 2029. 

As we have more information, I will post updates. In the meantime, the best plan is for all customers to ensure they are on supported versions of Nintex Automation/K2 Five to receive the updates under your maintenance agreement. We will not be updating K2 blackpearl, which reaches end of extended support at the end of 2025. If you would like assistance upgrading your K2 environments, reach out to your Nintex account manager and we’re happy to help.