10.0.x
541 201 9965 Email Website
Contents
:
Search:

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.

Why use an upgrade pack?

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.

How do I know if my site has modifications that will conflict with the upgrade pack?

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.

Applying an upgrade pack

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.

Before you begin

  • If you are using Full-Text Search on your site, log into the admin console and turn that off before doing anything else.
  • If you were encrypting the web.config on the site previously, you will need to log into the admin console, go to the Site Setup Wizard, and change the EncryptWeb.config option to No before starting the upgrade, or those keys will be unreadable. See this page for more information, or if you run into any trouble making that change.
  • Verify that you are using a payment gateway that is still supported. If you were using a gateway that is no longer supported, you’ll need to switch to a supported one. This can be a slow process, so it may be best to hold off on the upgrade until that new account is ready.
  • Backup your site files and database

Option 1 - Use diff tools

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:

  • Diff your site with an unmodified copy of the same version of AspDotNetStorefront that your site is currently running. This diff will allow you to quickly identify your modifications.
  • Now open a separate diff of the upgrade pack to the site you want to apply the upgrade pack to.
  • Push each file from the upgrade pack into the site one at at time while referencing your first diff for modifications. When you encounter a file that you have modified merge your modifications with the new file.
    • It is common to have to merge the following files:
      • /Web/AppSettings.config 
      • /Web/ConnectionStrings.config
      •  /Web/web.config
    • Look in the upgrade pack for /ItemsToRemove.txt file. If this file exists, remove the files referenced in this file from your project.
    • If you have the source code version of the software, or modifications in your admin directory, be sure to compile the site in release mode using Visual Studio.
    • Run the database upgrade script
    • Test your site to make sure the upgrade is functioning properly.

    NOTE: For version 10.0.7 PACK it is necessary to copy the ​\AssemblyReferences\Telerik.Web.UI.dll file to the site (web) \bin folder if not compiling source in Visual Studio.

    Option 2 - Just try it

    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:

    • Copy the files from the upgrade pack over the top of your existing site overwriting the existing files
    • Look in the upgrade pack for /ItemsToRemove.txt file. If this file exists, remove the files referenced in this file from your project.
    • If you have the source code version of the software, or modifications in your admin directory, be sure to compile the site in release mode using Visual Studio.
    • Run the database upgrade script
    • Test your site to make sure the upgrade is functioning properly.
    NOTE: For version 10.0.7 PACK it is necessary to copy the ​\AssemblyReferences\Telerik.Web.UI.dll file to the site (web) \bin folder if not compiling source in Visual Studio.


    Actions
    Print This Article
    Bookmark
    Email This Article
    Previous Article
    Next Article

    Was this page helpful?YesNo