Next: 1.4.3 Adjustments to Wizard
Up: 1.4 Using SiteServer Commerce
Previous: 1.4.1 Creating the Commerce
After verifying the goodness of the foundation build in the
previous §, you can get a VI project into which you can
introduce the XASP sources. This recipe is at a little
higher level than the previous one.
- Create the VisualInterdev project, specifying the site
you created with the Site Builder wizard as the existing
site on which the project is based.
- When the project is created, create two new directories
under the site root, ``custom'' and ``generic''.
- Copy the same-named directories from the XASP zip to
the local project directories (i.e. to custom and
generic copying subdirs as well).
- Add the new dirs to the master web and synch the project
view.
- Open global.asa in the root of the project and save it as
global.asa.mssc.
- Replace or merge global.asa from the zip with that in the
project.
- In the MMC, enable session state, execution and if you want
to use the VI debugger, debugging for the site.
- Confirm that the Perl AnySupplier DLLs are installed and
working properly. Easiest way to do this is by starting the
AnyFront utility and logging onto the database.
- Check ECatalog.inc and default.asp in the generic directory
and make your initial adjustments.
- Synch the local VI project with the master web.
- Test Web App. If you've built the sample E-Catalog you
should be able to browse it's content.
juan@acm.org