Home > Upgrading > Using Upgrade Packs
Using Upgrade Packs
To make upgrades a bit easier we’ve introduced the concept of an upgrade pack. An upgrade pack is a partial release of AspDotNetStorefront that only includes the files that have changed from one version to the next. When applied properly a finished upgrade pack installation is identical to an upgrade done using a complete copy of the code.
Upgrade packs are ideal for merchants who are one version behind, and do not have any major modifications. If your modifications are in files other than the files included in the upgrade pack, than the upgrade pack can be applied by simply dropping the files on top of your existing development or staging site, and running the upgrade script on your database.
We recommend that you use a file diff tool to identify your modifications. This can be tricky though. If you can’t use a diff tool you will not be able to be sure that your modifications will not conflict with the upgrade pack. In general, if you only have modifications inside your skin folder you can be reasonably sure that an upgrade pack will work for you.
First you need to decide whether you have the “source code” version of the software or not.
If you own the source code version you’ll probably want to use the source code upgrade pack. If you don’t own the source code version of the software, than you will want to install the non source code version. Be careful here. If you install the non-source code version and you’ve got source code modifications you will lose them. It’s best to check with your previous developers if you are not sure.
Grab the appropriate source or non-source version of the upgrade pack from http://license.aspdotnetstorefront.com/
* Disclaimer - Always perform an upgrade on a staging and/or development environment before upgrading your live site. Upgrade packs are not designed to deploy to your live site. You should deploy from your staging site to your live site once you have tested everything to make sure it works properly.
This is the preferred method, but it is also the most technical. Using this approach allows you to precisely identify modifications you’ve made and how diffifult a merge of your changes might be if necessary. You may need a developer’s help with this part. We highly recommend using software called Beyond Compare for this process.
In general you need to:
We always recommend that you perform an upgrade in a development and staging environment. If you’ve got a separate environment setup for testing you can apply the upgrade pack to that environment and then do thorough testing to make sure all of your modifications are still working as you expect before deploying to the live site.
To apply the upgrade pack: