For the longest time, Octopus and Tentacle have been built against .NET 4.0. We’d wanted to move to 4.5 since it first came out, but there was a problem:
- 4.5 is an in-place upgrade over 4.0
- If we built Octopus (or especially Tentacle) for 4.5, 4.5 would have to be installed on your servers
- There are a few minor breaking changes in 4.5 that could break applications that weren’t tested with 4.5 installed
- While these don’t affect Octopus/Tentacle, they could affect your other applications
- Bonus: .NET 4.5 isn’t supported on Windows Server 2003
Over time these arguments are holding less and less weight. .NET 4.5 was released in August 2012, so most applications that encountered these issues should have been fixed by now. Windows Server 2003 hit its end-of-life earlier this month, so there’s no reason we should continue to support it either.
There’s also a very compelling reason for us to switch to .NET 4.5: .NET 4.0 is limited to TLS 1.0. Moving to .NET 4.5 allows us to use TLS 1.2 for all future Octopus/Tentacle communication. It will also allow us to use newer 4.5-only libraries, like the latest Azure libraries.
For these reasons, Octopus 3.1 (and Tentacle 3.1) will require .NET 4.5. You can continue to use previous versions of Octopus if you’re unable to upgrade to .NET 4.5.
Tags:
Related posts
Certificates Feature
Certificates can be uploaded in PFX, PEM, or DER formats, and may include private-keys. They can be scoped to Environments and\or Tenants.
Deploying to no targets
As part of Octopus Deploy 3.8.7 we released a new feature related to Elastic and Transient Environments that we thought warranted a call out.
Octopus Deploy 3.7 - Effortless step templates
The new release of Octopus Deploy steps it up a notch by improving the UI for adding a step template, providing direct access to community step templates from a project's deployment process and improving the management of step templates in the library.
