🚀 go-pugleaf

We have a team of about 15 people who have been developing in separate
versions of BCB.  Most development has been done in BCB1, but some work
has been done in BCB3 and BCB4, with a mix of different patch/update
levels.  Many PCs have more than 1 version of BCB on them, but all are
using the Professional version.

We would like to bring everyone up to the same version + patch level
with the least amount of disruption possible.  The target machines are
all PCs, some Win98 and some NT.  I have read all available online
information reguarding upgrade gotchas, and I read this newsgroup
regularly.  Any and all advice is welcomed, and appreciated.  AFAIK, the
latest version is BCB4 with 2 patches available.  Now, my questions...

Is it necessary to uninstall all previous versions of BCB before
installing BCB4?

If uninstalling is necessary, should shared files (i.e. DLLs) be removed
during the uninstall?

After installing BCB4, should we install both patches separately? or
does patch #2 include patch #1?

Now, assuming each machine has BCB4 w/ update #2 on it, we will have to
port our software.  Obviously, all binary files must be recompiled.
Initial porting efforts have uncovered some rough spots, espescially
with OLE automation and 3rd party ActiveX controls.  This leads me into
the following questions...

Can you give a complete list of all the file extensions which should be
deleted + regenerated? (i.e. *.lib, *.exe, *.il?, *.obj, etc.)

Are there any components or libraries which were included in BCB1/3
Professional, which are not included in BCB4?  In other words, are there
any known backwards compatibility problems (besides those mentioned in
the online help)?

After a clean install of BCB4 + patches, we have re-imported our 3rd
party ActiveX controls.  However, in doing so, the type library
generator sometimes changes the interface between the control and our
code that was written in previous versions of BCB.  Is this the right
approach?  Is there any way to avoid going back and changing all
references in the old code?

Are there any other gotchas that would help expedite the process of
upgrading?

Thanks in advance to all who respond.

--
Dave O'Rourke
MIT Lincoln Laboratory


Sent via Deja.com http://www.deja.com/
Before you buy.