Andreu,
Here are just a few thoughts...I'm sure others have plenty to add.
By keeping your B7322 development workstation at Visual C++ 5.0, you will be
fine during development, checkin, and checkout.
Package builds will be a slightly different matter:
1 - You will need to build workstation packages from a workstation with
Visual C++ 5.0. And even though the results of the package are stored on
the deployment server (with 6.0), that is no problem. You just need the
actual build of all the c components to happen with 5.0.
2 - Server packages are where you will have the biggest challenge. Since
the build process for these takes place on the destination enterprise
server, there are a few things to consider. A) Are you moving to a new
enterprise server when you upgrade? If so, yippee!!! You can put 5.0 on
the old server and 6.0 on the new server and have no problems. B) You are
working with one server for both releases in which case you're not going to
be a happy administrator. The server needs to go to 6.0 for the new
release, which means no more server packages on the old release. (Note,
some may argue that you could still deploy certain types of objects that
don't involve the compiler, but that's a bit tedious.)
My recommendation is that you decide why you are continuing development in
the old release and set some rules. For example, emergency fixes for
production are quite understandable. And you hope they don't involve
objects that need to be deployed to the enterprise server. Or you go
through the process of determining which objects can be deployed to the
server without the compiler being involved and set rules around that.
If you are looking at an upgrade that may take a long time (<- you define),
then you may want to consider doing your initial dev/crp in XE on a separate
enterprise server...not anything scaled up for real production, but
something to get through the initial testing. When you are ready to cut
over to production on xe, then development would be finished there anyway.
Anyway, since you are coming from 7322, there are a lot of CNC guys out
there that have helped many clients through this predicament. Find one of
them for a planning session, and you can come up with a plan of action that
suits your needs.
Good luck to you.
>From: Andreu_Valls <
[email protected]>
>Reply-To:
[email protected]
>To:
[email protected]
>Subject: XE Upgrade ~~0:1205
>Date: Thu, 16 Nov 2000 02:12:14 -0800 (PST)
>
>Hi,
>
>Upgrade 7.3.2.2 to Xe
>NT and Oracle (Deployment and Enterprise)
>
>We want be sure that we can develop in 7.3.2.2 during the upgrade process.
>
>It will be necessary to change the Visual C++ from 5.0 to 6.0 in the
>deployment, Enterprise and Workstation.
>
>We can maintain a workstation in the old version (this is no problem for
>us) but we don't know if the Visual C++ can give a problems in the
>Check-in, Check-out, Building Packages,...
>
>Has anybody proof the same case ?.
>
>Thanks in Advance.
>
>
>
>--------------------------
>Visit the forum to view this thread at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=1205
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at
http://www.JDELIST.com
>*************************************************************
>
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.