Board index » cppbuilder » Re: caveat on installing C++Builder 2007 on the same machine with BDS 2006 installed

2007-06-19 09:23:43 PM
cppbuilder20
Rudy Velthuis [TeamB] wrote:
Different code, different bugs, different (or at least new) methods and
properties:
Any code which relied (intentionally or not) on known buggy behaviour
within the BDS2006 BPLs is unlikely to work right with the new ones.
- Roddy
 

Roddy Pratt wrote:
that would break that compatibility.
--
Rudy Velthuis [TeamB] rvelthuis.de
"We must all hear the universal call to like your neighbor like
you like to be liked yourself." -- George W. Bush
 

Andreas Hausladen wrote:
Speedup? You would know more on this than I do ;-)
- Roddy
 

{smallsort}

Roddy Pratt wrote:
in BDS2006 were caused by installing D2007 on the same machine and
later fixed with a D2007 patch or CB2007 installation. But this type
of interaction between the two IDEs is important information as well.
I am testing in a supported environment - CodeGear says they can be
installed side-by-side.
Same situation occurs with D2007 and CB2007. Results may differ if you
have just one installed or if you have them installed as a suite. Both
configurations are supported. Actually, there could even be
interactions with older BCB or BC++ versions that I have installed -
or that the person filing the QC report has installed. Or the version
of IE, for that matter.
That's why when I can't reproduce a QC report I encourage the filer to
provide more information in the areas that look like they could be
related to the issue. We live in a real world, and RAD Studio is not
intended to be used only in a "clean room" situation, and most of my
testing is not done that way either.
That being said, I find in most cases bugs that are reported against
BDS2006 can be reproduced on my machine if the information provided in
the reports is adequate for testing. In cases where there is an issue
with the environment, I can always test in a clean VM, but that is not
necessarily an exact copy of the user's environment either - it just
eliminates some possibilities.
- Leo
 

Leo Siefert wrote:
BDS2006 - does your D2007 start exhibiting a range of BDS2006 bugs?
Or, maybe worse yet, install BDS2006, D2007 and then BDS2006 hotfixes.
I think you might get a mixture of BPL versions that could be a
nightmare to untangle?
- Roddy
 

Roddy Pratt wrote:
doesn't, then we can always file QC reports. I've experienced some
horrible side-effects from patches to MS apps - completely disabling
other ms apps sometimes.
- Leo
 

In article <46673adb$ XXXX@XXXXX.COM >, "yhv" < XXXX@XXXXX.COM >
wrote:
what was the install/uninstall order and where were the .bpl files)
--
-David Dean
CodeGear C++ QA Engineer
<blogs.codegear.com/ddean/>
 

In article <46791e62$ XXXX@XXXXX.COM >,
"Roddy Pratt" < XXXX@XXXXX.COM >wrote:
--
-David Dean
CodeGear C++ QA Engineer
<blogs.codegear.com/ddean/>
 

In article < XXXX@XXXXX.COM >,
"Roddy Pratt" < XXXX@XXXXX.COM >wrote:
please get the details into QC so that they can be fixed.
--
-David Dean
CodeGear C++ QA Engineer
<blogs.codegear.com/ddean/>
 

David Dean wrote:
Windows Vista Business, 64-bit edition, 2GB RAM
Install order:
1. BDS2006
2. BDS2006 patches and updates, all the way to 10.
3. Copy all .bpl files from SysWOW64 to BDS2006\Bin folder.
4. Install CB2007.
5. Run CB2007 -works fine.
6. Run BDS: starts loading, but when it reaches bcbide100.bpl, I get this
error:
Exception EPackageRegistrationException in module coreide100.bpl at
000DCB21.
Registration procedure, Cppproject.IDERegister in package C:\Program Files
(x86)\Borland\BDS\4.0\Bin\bcbide100.bpl raised exception call EOleSysError:
OLE error 80131040, ClassID: {F8FEDD39-E3CE-4B8D-A657-9CA24686881F}.
Clicking ok, gives me this error:
OLE error 80131040, ClassID: {F8FEDD39-E3CE-4B8D-A657-9CA24686881F}
And BDS basically crashes.
If you want me to give you some more details via email, I'd be more than
happy to.
Jon
 

In article <468125d0$ XXXX@XXXXX.COM >,
"Jonathan Benedicto" < XXXX@XXXXX.COM >wrote:
know how to contact you if I need more info.
--
-David Dean
CodeGear C++ QA Engineer
<blogs.codegear.com/ddean/>
 

David Dean wrote:
Jon