Ensuring the software we develop is future-proof is a core fundamental of our software development services. We make sure the software we create is developed to work for clients in the long term. You don’t want to be delivered a solution that isn’t future-proof and can’t easily grow as your needs change. Here at BIThub Lancaster we are passionate about developing software that works for clients now and in the future. In this post we explore two areas in which we ensure we are developing future-proof software.
Keeping up to date
When developing software it’s important that the 3rd party components (E.g. the framework it’s built on) are up to date . This enables better security for your software because when support (from the 3rd party) ends so do security fixes. Keeping 3rd party components up to date also means that software changes can be implemented more dynamically. This is because you have access to the latest features giving more options for future development.
.NET Core (From Microsoft) is an open-source, managed computer software framework for Windows, Linux and macOS that we use for a large amount of our back-end solutions. .NET Core 2.2 has an end of support date of the 23rd December 2019 with older versions already being out of support. This means they are not getting or going to get security fixes unless they are updated.
The below table provides information on which .NET Core versions are currently supported, release dates of new versions and dates for End of Support.
|Version||Original Release Date||Latest Patch Version||Patch Release Date||Support Level||End of Support|
|.NET Core 3.1||Scheduled for November 2019||Will be LTS when released|
|.NET Core 3.0||September 23, 2019||Current|
|.NET Core 2.2||December 4, 2018||2.2.7||September 10, 2019||Maintenance||December 23, 2019|
|.NET Core 2.1||May 30, 2018||18.104.22.168||September 10, 2019||LTS||At least three years from LTS declaration (August 21, 2018)|
|.NET Core 2.0||August 14, 2017||2.0.9||July 10, 2018||EOL||October 1, 2018|
|.NET Core 1.1||November 16, 2016||1.1.13||May 14, 2019||EOL||June 27, 2019|
|.NET Core 1.0||June 27, 2016||1.0.16||May 14, 2019||EOL||June 27, 2019|
We don’t expect all clients to know the above information or even the framework your software was built on. However for some of you this may already be triggering alarm bells.
Well structured application
There are a number of methods that can ensure that future software changes can be made with low impact; saving time and money. These methods include:
- “Loose coupling” – where the software is developed in sections so changes and updates can be rolled out to those sections independently.
- Full coverage testing built in – To ensure the entire application is tested after any changes
These are just two of the many methods Bristol IT Company use to develop future proof software.
All of our software comes with support packages which includes keeping on top of what updates need doing but also a commitment to getting them out as soon as possible. Not every software provider does this. So ask yourself, do you have a maintenance contract with your software developer? Is your software built on the most up-to-date framework? If the answers are no, or if you’re not sure, get in touch to see how we can help.