Upgrading Your Store to a Newer Version

Annual Upgrades Contract

If you want to receive free technical support AND product upgrades (for the product version you order) for one (1) full year, you can select this option during checkout when purchasing our product in AspDotNetStorefront. Without this option, we offer free technical support for 30 days, and free product upgrades for 30 days.

This option allows you to ensure full coverage for 12 months from date of purchase to stay current in both software and support services for a single license purchased.

If you have multiple licenses, you would need an upgrades contract for each license. Contact us if you need to discuss quantity discounts.

If you are purchasing this contract after you placed your original order, it will add 12 months to whatever the date of when your contract last expired. Select the contract that matches your storefront version:

• ML - $399

li>

ML/DNN - $399

li>

IS - $399

li>

ML64 - $399

Upgrading Procedures

• From v6.2.x to v7.0

• From v6.0.5.1 to v6.0.5.4

• From v5.x.x to v6.x.x

Cell Phone Notification Changes in v6.1:

Starting in v6.1, in the SMS cell phone notifications, they must setup their AppConfigs to be their FULL phone e-mail address (not just the phone #). The AppConfig:Dispatch_CellCarrier is no longer used:

AppConfig:Dispatch_ToPhoneNumber

The name of this AppConfig is now a bit incorrect, but it works fine, if you just follow the instructions below. We didn't want to rename the AppConfig, as most users already know about this one.

Prior to v6.1, you would enter

AppConfig:Dispatch_ToPhoneNumber=(480) 555-1212 (for instance)

In v6.1, you must now set it as the full e-mail address of your phone, e.g.:

AppConfig:Dispatch_ToPhoneNumber=4805551212@tmomail.net (just an example, for T-Mobile).

General Upgrade Notes

1. After an upgrade, you may have missing string resources, so loading the strings again from the new version Excel file will usually fix this (e.g. if you see missing strings like common.cs.4, shoppingcart.cs.15, etc on your site). See Reloading Site String Resources.

2. If errors are taking place while doing the upgrade, try to install the upgraded version, on a BRAND NEW 'MASTER' database. Always make note of every single error you encounter. If you still need help, contact us.