> different VB developers. Even with good communication, I'm having a
> hard time understanding how you could have two lines of development on
> a VB form.
I'll admit, it *is* tougher, but I still think it's doable.
For one thing, how often do you expect to do exactly parallel development on the exact same VB form? I wouldn't normally expect two
developers to be working on the same source file at the same time, regardless of its type. Occasionally, perhaps, but not normally.
I realize that my development effort and philosophy aren't the same as everyone else's, but if I had two features that required work
in my system, and they were so related that they had dependencies on the same form, I'd assign them both to the same developer. If
they were unrelated, but depended on the same form, I'd look at whether I needed to do some redesigning. :-)
If something like that *is* necessary, Subversion's locking feature should suffice to keep the two in sync, as only one of them
would be able to lock the form, and its associated FRX, at the same time. It believe there is a property to which Subversion is
sensitive that tells the client that a file must be locked before being edited. You could set that property on all of your forms
that have FRX files associated with them, along with the FRX files, of course.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jun 27 17:16:26 2005