Thanks for the suggestion, Brass. Could you explain how your system
works a little more? What do you mean by a standard developer build?
Do you have to update your login script each time someone adds or
deletes a reference?
Thanks,
Greg Pinero
On 5/24/05, Brass Tilde <brasstilde@insightbb.com> wrote:
> > Visual Basic 6. For some reason each developer has different
> > references at the top of this file, and no matter how many
> > times we sync them, I guess Visual Basic changes them back
> > when you open them.
>
> The references in the VBP file are set there by the IDE when you open the
> project. If one developer has a registered DLL or OCX control in one
> location, and another developer has it in a different location, the IDE will
> search the registry for the class-id of the DLL or OCX and replace the path
> in the VBP file with the one in the registry on the machine on which the
> project is opened.
>
> We manage this brain-dead behavior (why does the location matter as long as
> it's registered, when you can get the registered location any time you want
> by looking in the ... registry) by simply having a standard developer build
> for our machines, and a login script that makes sure the items are all in
> the expected location.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 25 18:13:05 2005