Once your application is protected with the SoftwareKey System, there are really no limitations on how you initially deliver the software to your customer's computers. One of the most commonly asked questions has to do with installing subsequent updates (patches) and new versions of your software (both minor and major), which we will discuss in this post.
You will typically install some type of installation utility on your development workstation to build a package used to deploy your software onto a new computer. There are many free and commercial installation utilities available, some using a visual interface for configuration and others that require writing a script file. Once the installation file is created, you can transmit the protected application via any form of physical media (CD/DVD, thumb drive) or electronic medium (email, web site, online storage services).
How you deliver the software and how you update the software doesn't change how our licensing works, since the software will look at license files in external locations, unaffected by the installation utility.
For customers who have a license to use your software, there are Electronic Software Delivery (ESD) features available in SOLO Server with a lot of power and control. You first upload the software and configure the ESD settings. When the customer receives their license, they log into the Customer License Portal and click on the Downloads. They will see a list of licensed software and the option to download, with the following capabilities:
As a side note, you can reduce support costs by keeping your customers updated to the latest version of your software using a SOLO Server included feature to notify the customer when a new version is available. An example update notification dialog for your application can look like this:
The installation file used to upgrade your software can take any approach:
As long as the new version of your software's source code or wizard settings uses the same license file names, locations, and encryption key data, and the installer doesn't modify these external files during an upgrade or patch, installing the updated version of your software should run without requiring re-activation.
All you need to do is change your protected application to use different license file names, locations, and encryption key data in the source code or wizard project settings. If the customer has Version 1 installed and activated on their computer, then later installs Version 2, re-activation will be required because Version 2 is using completely different locations for the license files.
Most installation utilities will add your software application to the list of installed software in the Windows Control Panel. The customer can use this Windows feature to remove your software. Depending on your business requirements, you may or may not want to have your uninstallation process remove the license files from the computer. Removing the license files will likely require your software to be re-activated if they choose to re-install the software. For computers which are connected to the Internet, it is even possible to have the uninstallation utility automatically and silently deactivate this computer's license with SOLO Server, freeing up this activation for a new computer to use.
The SoftwareKey System has many features for automating the deployment of your software, and you have control over when customers should be required to re-activate when updating the software.
If you have questions about deploying your software when using the SoftwareKey System, feel free to contact us.
Mike Wozniak is one of the co-founders of SoftwareKey.com and responsible for marketing, content and product strategy. When he isn't plotting new ways to help customers solve licensing and business automation challenges, he likes to travel and entertain guests who come to visit the Orlando area. He also writes most of the licensing tips here.
Time for Blast Off: New SoftwareKey Support Portal Launched!
Allowing customers to purchase additional software activations
Using a Counter Value in Licensed Applications
Choosing a Wizard-Based Licensing Client
7 Ways License Automation Increases Revenue and Saves Time
Licensing Client: Wizard-Based or Advanced SDK