Kbase P57636: Things to be aware of when migrating the Dynamics web UI app
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/12/2003 |
|
Status: Unverified
GOAL:
Things to be aware of when migrating the Dynamics web UI application from 2.0A to 2.1A
GOAL:
Is there a checklist for migrating Dynamics web UI from 2.0A to 2.1A ?
GOAL:
What to be aware of when migrating Dynamics web UI from previous version to 2.1A
FACT(s) (Environment):
Dynamics 2.0A
FACT(s) (Environment):
Dynamics 2.1A
FIX:
If the migration takes place from 2.0A or 2.0ASP1 to 2.0ASP2 or 2.1A
(i.e. From HTC to JS architecture), then there is a Dynamics web migration
document with checklist of things to consider available at PSDN whitepapers:
"Overview to Migrating Web Applications for Progress Dynamics· Version 2.0A02"
However, if one is moving from 2.0ASP2 to 2.1A (i.e. already with JS
architecture and moving to the next release) and has followed the
recommendations for JS object and CSS extensions, then there should
be no required modifications except the default.htm (layout) file changes.
If one modified the default.htm, then it is required to take default.htm
from 2.1A and reincorporate any changes that have been made to this file.