to Axapta, so some of my questions probably sound pretty dumb.
Our Axapta programmers code in a development environment using fat 3-tier
clients. We then copy the folder, rename the folder with the name of the
test environment, delete the aoi file, turn back on the aos servers which
rebuilds the aoi file; we then recompile and resync. However, we still get
forms that in the development environment are different from in the test
environment (lable names, or field that don't calculate, for example). In
the test environment we use thin 3-tier clients.
We've found out that hotfixes just mess everything up, which is why we copy
the entire environment.
Is there something wrong with this approach that would cause us to have
these anomolies? Is there a best-practice method of moving code from
development to test environments.
Thanks,
Andrew
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
