This is a preview version of Cyotek's blog and may be missing functionality and/or unstable. Please visit for the current version of the blog.
If you encounter any problems using this preview site, please contact us with the details.

Archived posts for All of 2016

Introducing CopyTools 2.0

Cyotek CopyTools 0 Comments

Out of our product range, my own personal favourite is CopyTools. This program has been working in the background for years quietly ensuring every digital file of import is backed up, and even performing some maintenance tasks such as downloading Azure SQL databases.

As with most software it is by no means flawless, and recent (internal) builds compounded the issue rather than improving it. Although it was originally supposed to support remote sources such as FTP servers and Azure blob storage, the model was too rigid and in order to add this support would require massive changes to program's core, instead of supporting the extensibility model that most Cyotek products offer.

Read More

.NET 4.6 is now required for all Cyotek products

All Products 0 Comments

It's been a year since I announced that WebCopy would be moving from Microsoft .NET 3.5 to 4.5, therefore ending XP support. As Microsoft have now discontinued support for 3.5 and 4.5, all Cyotek products will be using .NET 4.6 in subsequent builds, starting with the nightlies.

This change will mean that no future builds of our products can be used on Windows XP. Vista Service Pack 2 will be the minimum supported operating system.

Read More

Introducing nightly builds

All Products 0 Comments

At the start of the year, all of our build processes were finally CI friendly and wired up to Jenkins. Now, whenever a commit is made to our SVN repository, the relevant products are built, tested, and deployment artefacts produced.

As well as building the setup programs our users ultimately install, the build process now also extracts all the files and tests them for dependency errors, using a slightly more improved version of a sample I posted some years ago. This will hopefully avoid future issues where we introduce a new dependency then forget to update setup with it, as has happened in the past.

Read More