Makes sense. I'm about to just give up on the branching/merging plan
for our VB developers. The general consensus seems to be that it's
impossible to effectively branch/merge VB projects because of the
frm/frx marriage. Very disappointing, since this is exactly what we
need to do with this team.
<sigh>
On 6/27/05, Brass Tilde <brasstilde@insightbb.com> wrote:
> > I was just curious if anyone has "best practices" for handling the
> > binary frx files for Visual Basic 6.0.
>
> Whether or not it's a *best* practice, we've simply decided not to merge them. We'll likely use the locking feature present in the
> 1.2 version of Subversion to handle this. It may also be necessary to lock the FRM files, since a change to one of them can result
> in a change to the unmergeable FRX file, but we'll have to see.
>
> Brad
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jun 27 15:56:36 2005