.NET Framework

You may have noticed that we always release our products or updates in the latest version of the .NET Framework. This can cause frustration for many users who are still using older versions of Windows but why do we follow this course of action? It’s not an easy decision, certainly not when a user is in need of our software but is unable to run it.

The reason why is quite simple. We know that it is impossible to keep all of our software up to date all of the time, especially since this is a tiny company with few people that does not generate any profit. The developers here don’t ask for any money. We don’t need donations to keep the site up and running (at least not for the coming two years) but we can make an exception for the occasional cup of coffee (so feel free to give us that extra boost of energy)! Rest assured, however, we don’t need the donations (for now) and we’re more than happy if our software is able to solve an issue or make life easier for you.

Seeing as we cannot constantly update and renew every product of our product line (however we do update them in case of emergency a.k.a. bugs). Sometimes, this means that a product can go months or perhaps even years (although this hasn’t happened yet) without updates and as time evolves, so does the .NET Framework. More and more people are upgrading to newer versions of Windows and we have to make sure that we’re using the latest and greatest features of that new operating system version so that our applications run smoothly on your machine. This means making some sacrifices in regards to the required system specifications.

Joke image

Most of our complaints come in the form of Windows XP (surprisingly not Vista) support. Windows XP support is completely depricated by now and the companies and people who are still using this version of Windows are in dire need of an upgrade. In terms of security alone, Windows XP does not recieve any more updates from Microsoft which means that if a vulnerability is found it will not be patched. This makes online banking and even logging into websites a serious threat to your security. We cannot, in good conscience, create products for a version of Windows which has been found to contain vulnerabilities but is no longer being patched.

In short: we think about the future, we want to be able to support our products on newer versions of Windows and will always try to include the latest features into our products so that it runs as intended on your machine.

Portable versions

Portable versions of products are great when your machine is not connected to the internet (for example due to malware in the case of DeadLock) or when you don’t want to install a product because you’re only going to use it once or twice. We get the occasional e-mail about releasing portable versions of our products but let me assure you that we will put more effort and time into making this a reality.

It’s 2017 and this means that we’re going to set some goals for the future. We will try to release our software (if applicable) not only in the form of installers but also in portable versions. In the past we have released portable versions of some of our products, but starting this year we will try to release more products and updates in a portable form (the installer versions aren’t going anywhere though).

The reason why we prefer using installers is because of user error (or preventing user error). In previous work experiences, it has come to our attention that downloading a zip file containg an executable and it’s portable libraries can cause issues when only the main executable is extracted from the archive. Our thoughts behind using installers are simply to prevent errors that occur due to a missing library or a file that was accidentaly deleted. But we realise that this should not prevent us from releasing a portable version.


Phew, it’s finally over. The first ever Dev Blog is finally complete. One would say that as a programmer, I’m used to typing so much but it’s quite different when you’re writing code versus writing normal human readable text. Not that I dislike writing these posts, it’s something entirely new to me.

In any case, I hope you enjoyed reading this dev blog and perhaps we’ll make another one of these in the future, if ofcourse you’d like that. Feel free to leave a comment below or contact us if you have any questions!

Pin It on Pinterest

Share This