consider following few tips from my own experience to make test and
development environments running smooth:
- use separate databases for test and dev environments (make backup and
restore it as Hemant has adviced in the previous email);
- you don't actually need to copy whole application directory, only files
from your layer (for example if you work in USR this mask can be used:
*USR*.*)
- always stop AOS and start Axapta in 2T before you copy application files
from development environment;
- don't use AOS to rebuild indexes in test environment after update, use 2T
instead.
hope it will help,
best regards,
Yurii
On 11/11/05, Hemant Kumthekar <[EMAIL PROTECTED]> wrote:
>
> Hi Andew,
>
> Can you please expalin what folders are copied and renamed?
>
> If you loook at the installation directory , you have a structure
> something like this
>
> Navision >> Axapta Application >> Appl >> and under Appl you can have sub
> folders which can AXTEST , AXDEV , Standard. So if your developers do
> development in AXDEV program directory , you can just copy the AXDEV and
> restore it over AXTEST, also you would like to take a SQL backup of database
> connected to DEV environment and then restore that SQL backup on TEST Db
> using SQL Manager. Be careful when you are doing these tasks, in this case
> you are replicating whatever is in DEV environment on to TEST environment.
>
> In case you are trying to just copy certain changes , then you may be
> better off by exporting with Lables (normally you should have created a
> Label file) and then import the project in TEST. Take care about the label
> file in TEST environment.
>
> Hemant
>
> Andrew Staples <[EMAIL PROTECTED]> wrote:
> Sorry for the newb questions, we are migrating from an old RPG-based
> system
> 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.
>
>
> ---------------------------------
>
>
>
>
> ---------------------------------
> Yahoo! FareChase - Search multiple travel sites in one click.
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
[Non-text portions of this message have been removed]
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.
