Re: seeking guidance to solve compatibility problems in automated buil
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Fri, 1 Dec 2006 18:14:36 -0500
"Richard Winks" <RichardWinks@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D4AA1219-E2DB-48D7-A7BD-037821364CD1@xxxxxxxxxxxxxxxx
I have inherited a product written exclusively in Visual Basic 6.
The product consists of a single exe and a number of dlls.
Dlls are interdependent and are self-registering.
The problem I have is that I extract the component projects from sourcesafe
as the developer checks it in, build it (vb6 /makedll...), register it and
then rebuild the dependent dlls or the exe, I get reference errors.
If I open the failed component project in VB6, and reselect the reference,
by examining the saved .vbp file I find that reference GUID's have changed
for the built reference.
I understand that this has something to do with binary compatibility but the
developers have assured me that it is turned off.
And that's the problem. It should be turned "on". You want to maintain binary compatibility, not break it. If binary compatibility is turned "off" (meaning either the No Compatibility or Project Compatibility option is set), then every time you recompile that component, you'll have to recompile EVERYTHING that uses it.
Can anyone direct me to a definitive methodology for handling a situation
like this. I find some vague and unclear references to using Visual Basic
Group (.VBG) projects but I tried building one large group including the main
exe and all dependencies and run into similar problems.
See this:
http://www.vbsight.com/BinaryComp.htm
(courtesy of Ken Halter)
--
Mike
Microsoft MVP Visual Basic
.
- Prev by Date: Re: Make sure file path is there
- Next by Date: Re: What is the latest version of VB?
- Previous by thread: How can I define a "Change" event for a variable?
- Next by thread: Re: seeking guidance to solve compatibility problems in automated
- Index(es):
Relevant Pages
|
