FYI: AspDotNetStorefront to Interprise Suite eCommerce Migration

Introduction:

Welcome to the Interprise Suite eCommerce (ISE) web application.

If you are upgrading from AspDotNetStorefront for Interprise Suite there are a couple of additional steps you will need to take before you will be able to use the ISE with your custom skins and/or custom pages. These changes are necessary due to the recent update of all references from “AspDotNetStorefront” to reference “Interprise Solutions eCommerce” or ISE instead. These changes did not affect functionality; however, they can potentially break any custom coding that was done to the storefront site including: Skins, XML Packages, and other custom code. This document will detail the changes that were made, any changes that were not made now but will potentially be made in the future, and how to update any custom code that may have been affected by the changes.

Here is what was changed:

1.     File Names - All code files have been renamed, including the solution, project files and compiled DLL’s.  Note: The Storefront web service was not renamed as this would break the default web service name in IS.

2.     Source Code Headers - All source code headers (comments) have been updated.

3.     Assemblies (DLL’s) - The assemblies ASPDNSFCommon, ASPDNSFControls, and ASPDNSFGateways, which compile into DLL’s have been renamed to InterpriseSuiteEcommerceCommon, InterpriseSuiteEcommerceControls, and InterpriseSuiteEcommerceGateways. The assembly info files for all included Assembly projects have been updated as well.

4.     Source Code - All source code (including hardcoded HTML and strings) and code comments containing references to AspDotNetStorefront were updated.

a.     Skin Files – All skins files were updated to use the new Namespaces and DLL’s.

b.     XML Packages – All XML packages were updated to use the new Namespaces and DLL’s.

c.     Web.config - Web.config was updated to reference the new Namespaces and DLL’s.

5.     Data - A new SQL update script was created to update the following:

a.     Update the App Config values (If we find AspDotNetStorefront, we replace it with Interprise Suite eCommerce).  The App config names were not updated as this could break 3rd party code.

b.     Updated all string resources.

c.     Topics were not touched as they did not contain any references to Storefront.

6.     EULA (End User License Agreement) - The ReadMe.txt file was updated.

Not changed, but probably will be in the future:

1.     Database – No changes to the database schema were made. There are several stored procedures that are prefixed with ASPDNSF_ that will potentially be renamed in the future.

2.     Web Service - The ISE web site contains a web service named StoreFrontService.asmx. This was not renamed at this time due to changes that would have needed to be made to Interprise Suite. This will potentially be renamed for the IS 2009 release.

Where customers could be affected:

1.     Skins - All skin files will need to be updated to use the new ISE classes.

2.     XML Packages - Any custom XML packages will need to be updated to use the new ISE classes. The code and functionality didn’t change, just the names.

3.     Web.Config - The web config will need to be updated to use the new ISE namespaces.

4.     Custom Code - Any custom code that references the StoreFront dlls or classes will need to be updated to use the ISE dlls or classes.

Upgrade Instructions:

1.     Make full backup of the IS database. 

2.     Make full backup of theweb site (every file). 

3.     Upgrade the database using IS Database Management Console.  

4.     Copy the files from the new ISE release to the web site (Only files found in /web). 

5.     Update Skins to ISE format (See Instructions Below). 

6.     Move the saved files back to the website for each of the following directories (overwriting our files if needed, so yours take priority).

a.     /images 

b.     /skins 

c.     /download 

7.     Update XML Packages to ISE format (See Instructions Below). 

8.     Move any custom /XmlPackages back into /XmlPackages. 

9.     Update any custom code to ISE format (See Instructions Below). 

10.  Update Web.config file to ISE format (See Instructions Below). 

11.  Re-edit the /web.config file using Interprise Suite Application Configuration Tool. 

12.  Consult the manual for further instructions as needed. 

13.  After your upgrade is successfull and you have confirmed the integrity of the upgraded database. Then you can delete that backup.

Update Instructions (AspDotNetSorefront to ISE)

Follow the instructions below to update skins, XML packages, web.config, and other custom code.

§  SKINS

·         Skin packages (i.e. Skin_1) will typically contain two .ascx files that will need to be updated following the simple instructions below. Skin packages may also contain XML packages. See the XML package section below for update instructions. Please note that any skins that ship with the ISE code have already been updated and can be used as a reference for these updates.

·         Template.ASCX:

• Replace: <%@ Control Language="c#" AutoEventWireup="false" Inherits="AspDotNetStorefront.TemplateBase" TargetSchema="http://schemas.microsoft.com/intellisense/ie5" %>
• With: <%@ Control Language="c#" AutoEventWireup="false" Inherits="InterpriseSuiteEcommerce.TemplateBase" TargetSchema="http://schemas.microsoft.com/intellisense/ie5" %> 
• Replace: <%@ Register TagPrefix="aspdnsf" Namespace="ASPDNSFControls" Assembly="ASPDNSFControls" %>

o    With: <%@ Register TagPrefix="ise" Namespace="InterpriseSuiteEcommerceControls" Assembly="InterpriseSuiteEcommerceControls" %>

·         Empty.ascx:

• Replace: <%@ Control Language="c#" AutoEventWireup="false" Inherits="AspDotNetStorefront.TemplateBase" TargetSchema="http://schemas.microsoft.com/intellisense/ie5" %>
• With: <%@ Control Language="c#" AutoEventWireup="false" Inherits="InterpriseSuiteEcommerce.TemplateBase" TargetSchema="http://schemas.microsoft.com/intellisense/ie5" %>

§  XML Packages

·         The ISE code ships with several XML packages all of which have already been updated. However, any custom XML packages or XML packages that have been modified will need to be updated as shown below. Please use the XML packages that were shipped with the code as a reference for these updates.

• Replace: <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:aspdnsf="urn:aspdnsf" exclude-result-prefixes="aspdnsf">
• With: <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ise="urn:ise" exclude-result-prefixes="ise">

• Replace all instances of: aspdnsf:
• With: ise:

§  Web.Config

·         The web.config contains the application settings that the website needs in order to function. Any references to the AspDotNetStorefront Namspaces and DLL’s will need to be updated to use the ISE Namespaces and DLL’s instead. These updates can be made by completing the following Find and Replace operations.

• Replace all instances of: AspDotNetStorefrontCommon
• With: InterpriseSuiteEcommerceCommon
• Replace all instances of: ASPDNSFISGUID

·         With: ISEGUID

• Replace all instances of: ASPDNSFControls
• With: InterpriseSuiteEcommerceControls
• Replace all instances of: ASPDNSFSiteMapProvider
• With: ISESiteMapProvider
• Replace all instances of: StoreFrontUserNameTokenManager
• With: InterpriseSuiteEcommerceServiceUserNameTokenManager
• Replace all instances of: AspDotNetStorefront (Match Case)
• With: InterpriseSuiteEcommerce
• Replace all instances of: aspdnsf (Match Case)
• With: ISE

The above replace of AspDotNetStorefront will cause the AspDotNetStorefrontPatterns to be renamed to InterpriseSuiteEcommercePatterns. For now this must remain AspDotNetStorefrontPatterns, so the following replace will need to be done to undo the changes.

• Replace all instances of: InterpriseSuiteEcommercePatterns
• With: AspDotNetStorefrontPatterns

§  Custom Code

·         Any custom code or code that has been modified will potentially need to be updated to use the ISE namespaces and DLL’s before it will compile and run on the web server. The following items should be taken into consideration when updating custom code. If possible use Visual Studio to ensure that the web site and custom code build before deploying to the web server.

a.             Namespaces

i.                AspDotNetStorefront was renamed to InterpriseSolutionsEcommerce.

ii.                ASPDNSF was renamed to ISE.

b.             DLL’s

i.                ASPDNSFCommon.dll was renamed to InterpriseSuiteEcommerceCommon.dll.

ii.                ASPDNSFControls.dll was renamed to InterpriseSuiteEcommerceControls.dll.

iii.                ASPDNSFGateways.dll was renamed to InterpriseSuiteEcommerceGateways.dll.

c.             Javascript

i.                AspDotNetStorefront was renamed to InterpriseSolutionsEcommerce.

ii.                ASPDNSF was renamed to ISE.

 

Terry Palmer
Professional Service Manager
Dimesoft Business Solutions
tpalmer@dimesoftinc.com

URL to Connected Business: http://www.connectedbusiness.com/HOME/tabid/36/Default.aspx

URL to Knowledge Base in Connected Business: http://www.connectedbusiness.com/FORUMS/KnowledgeBase/tabid/186/Default.aspx

URL to the article: http://www.connectedbusiness.com/Default.aspx?TabID=186&Contenttype=ArticleDet&Aid=125

Terry Palmer
Professional Service Manager
Dimesoft Business Solutions
tpalmer@dimesoftinc.com