how to use tsvn with excel & vba

[wilfried van ginneken]

I'm totally new in versioning but I'd like to try it for some old excel 2003 workbooks I've created once (just for personal use) and do need an update .
I've already been playing around a bit with tsvn and installed sourcetool.xla which seems to make it easy to integrate excel with tsvn but I don't succeed in completing the entire revisioning-process: check-out is ok, updating modules also, but after updating modules I cannot get them back in the workbook.
can anyone help me in describing which steps they follow to update their vba-coding?

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3057397

To unsubscribe from this discussion, e-mail: [dev-uns...@tortoisesvn.tigris.org].

[Friedrich Brunzema]

Doing a google search, there seem to be multiple versions of this tool. (which are you using?) Looks like the tool provides a basic "Save my macros outside of Excel in a text format" functionality, along with re-loading, SVN update, Commit etc.

The code project macros use TortoiseProc commandlines to execute the SVN operations. Here the author's Program Files are C:\Programme instead of c:\Program files. That is probably why things are not working. You will likely need to adjust the addin for it to work - it has likely nothing to do with Tortoise SVN.

Best,

Friedrich

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3057412

[Gunter Koenigsmann]

Instead of saving things outside of excel to get them saved in a text
format I always dreamed of a pre-commit-hook that works on the fact that
technically a docx file from word or a xlsx file from excel-file is an
ordinary zip archive. to get things like svn:keywords working it would
suffice to
- unpack the zip-archive before committing
- and zip it again using zero compression ( for the command line zip
utility the command- line flags that do this would read "-Z store" or
shorter "-0".
Additionaly setting the compression to zero would mean huge space
savings on the server:
- Subversion internally uses compression for storing files so the
files won't be saved in an uncompressed state on the server
- and subversion only stores the differences between the old and the
new version. If you change just a single word in an uncompressed file
chances are high that the change affects only a single line that
therefore has to be stored on the server.
If the file is compressed, file chances are high instead that
changing a single word in the uncompressed will affect the whole
structure of the result of the compression so subversion will have to
store big portions of a file regardless how efficient it normally is in
handling binary files.

Gunter.

Gunter Königsmann
R&D

Tel: +49 911-6559-6025
Fax: +49 911-6559-776747
www.semikron.com
gunter.ko...@semikron.com
SEMIKRON Elektronik GmbH & Co. KG
Sigmundstrasse 200, 90431 Nürnberg, Germany
Amtsgericht Nürnberg HRA 13650
Komplementär:
SEMIKRON Elektronik Verwaltungs GmbH
Amtsgericht Nürnberg HRB 21338
Geschäftsführer:
Thomas Dippold
Peter Frey
Harald Jäger


IMPORTANT NOTICE - The contents of this email and attachments are
confidential. If you are not the intended recipient you must not use,
copy, distribute or rely on this email and should please return it
immediately or notify us by telephone. While we take every reasonable
precaution to screen out computer viruses from emails, attachments to
this email may contain such viruses. We cannot accept liability for loss
or damage resulting from such viruses. The integrity of email across
the Internet cannot be guaranteed and SEMIKRON will not accept liability
for any claims arising as a result of the use of this medium for
transmissions by or to SEMIKRON.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3057596

[Friedrich Brunzema]

Günther,

Nice thought experiment, but I don't think it is going to work.  Subversion is based on the idea of storing and versioning files - you put something in and if you ask for it later you get the file back which is byte for byte the same.  Unzipping and storing the bits and re-assembling very likely means you can't get a byte-for-byte comparison match.

Also think about what happens when someone browses the file through http.  Instead of seeing the file, they see a directory, which contains the streams inside the zip.  Because you can have "directories" inside a zip file, what do you do - create an entire directory tree in svn?

If all you wanted was keyword expansion for Word/Excel/Powerpoint, I think it should be implemented differently (using the OpenXml API), and not in TSVN - either in subversion itself, or in an external program like SubWcRev. But is the feature really that useful for office docs?  Other rev. control systems like Git don't even have keyword expansion.

Best,

F

---

From: Gunter Koenigsmann <Gunter.Ko...@semikron.com>
To: d...@tortoisesvn.tigris.org
Sent: Tuesday, June 11, 2013 3:10:54 AM
Subject: Antw: how to use tsvn with excel & vba

[Gunter Koenigsmann]

Dear Friedrich,

If one would want to add this functionality directly to tsvn I totally
agree with you: A versioning system that alters the contents of files by
default can be an extremely bad idea. For example there is never a way
to guarantee that a .docx file will really be from word and therefore a
zipfile you can re-pack without damaging the data it contains and for a
system that is optimized on the security of the user's data one failure
would be one failure too much. This functionality also might not be a
task one would expect a versioning system to contain. But if anybody
would write a post-commit hook that recompresses word (and openoffice
files that aren't in the uncompressed .fodt format, that is) files
instead of writing a plug-in that stores the versioning information in
separate files - I would know somebody that would actually use it: This
task has about the right shape that it feels right to let a third-party
plug-in that is unrelated to the actual versioning system (but
automatically called by the versioning system) do it.

Kind regards,

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058076