This sounds like a build issue to me, with the twist that the target
file is also a source file. Like any other project, you really need to
perform a build (and test the result) before commiting changes to the
archive.
I recall that the TSVN project has a helper application to notify
users of commits. This might be of some use to your situation.
However, you really need to train the users in proper use of version
control, both in general and TSVN specifically.
On 1/24/08, Chad Knudson <cknudson_at_autodocs.com> wrote:
> My company does a lot of work in Microsoft Office templates in Word and
> Excel. Subversion handles these as binary files and that is okay with me
> but there are also the VBA project elements (VBA source code in modules and
> classes as well as binary forms). I would like to utilize Tortoise as our
> client for Subversion access and somehow manage to track the internal VBA
> project elements as well as the files as a whole.
>
> So far, I've written Microsoft Office AddIns to export the source code and
> binary form blobs to files and placed them in a subdirectory underneath
> where the template files reside. This gets me about 40% of what I need J
[...]
> To get to 100%, I need to be able to convey to knowledge workers that the
> file they are working on in Office is in revision control and give them some
> sort of notification if they need to update their copy prior to working on
> it etc. Most of our content workers only work in the document/spreadsheet,
> and not in the VBA side of things but we need to all be utilizing the same
> revision control mechanism to keep from someone getting out of sync or
> walking over someone elses changes.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-24 19:12:23 CET