Forum Discussion

MKS267's avatar
MKS267
Copper Contributor
Dec 01, 2021

Product Life Cycle Management on .Net Core

I am curious to learn if anyone else has the same challenge. 

We have software and provide support for 3 years which is built on .Net Framework and due to end of the support of .Net framework next year we're planning on adapting .Net6

Challenge is if we adopt .Net 6 there'll still be previous versions built on .Net framework which need support according to our 3 years support policy. 

- How do you handle this?

- Do you use patches?

Any ideas? 

Do you know any software companies or examples?

Thank you in advance. 

 

Console Apps

1 Reply

  • JamesMontemagno's avatar
    JamesMontemagno
    Icon for Microsoft rankMicrosoft
    Dec 03, 2021
    I would take a look at the Release Schedule for .NET -> https://dotnet.microsoft.com/platform/support/policy

    LTS releases like .NET 6 are 3 years and Current releases are 18 months. As far as "quality" goes there is no difference between current or LTS it is just the patch and support lifecycle of it.

    Some companies move only on LTS, however many more are shifting towards updating to each version of .NET as there are a lot of benefits to each release and easier than ever to update from version to version.

    .NET Framework 4.8 will be continued to be supported as long as it is installed on a supported version of Windows, which is a long time, but isn't going to get new features or big changes for perf like main line .NET will be so moving does seem like a win for you. https://dotnet.microsoft.com/platform/support/policy/dotnet-framework

Resources