Molle Bestefich wrote:
> For example I want to hook SubWCRev in as a Pre-Build event in Visual Studio.
>
> If I want to integrate SubWCRev with the VS integrated build system as
> it is now, I'll have to make some abomination of scripts that on
> pre-build runs a SubWCRev and moves some files around to replace the
> original source file with the SubWCRev replacement, and when the build
> finishes move the files around again. *If* the build finishes. And
> I'll be really mad when it doesn't and I have to go through all my
> source files and replace back numbers with $WCREV$ and such :-).
> Especially if I've missed that the post-build script didn't run for
> some reason, and I've later modified a lot of code and checked in and
> compiled and released. Then I'll be mad.
You should use SubWCRev the same way TSVN does: use a template file
which then you can create the file you use in VS.NET from.
We had SubWCRev as a pre-build step in the TSVN build process too. But I
removed it from there and put it in the batch file because I sometimes
don't want it to run everytime I build the project.
Stefan
> Seeing as this is a good thing to do on all your projects, it would be
> very neat if SubWCRev could be made to just modify the original source
> files, with a single command like "SubWCRev --update", and all that
> one had to remember would be to put "SubWCRev --update" in your
> pre-build event in all your projects.
How would that work? I mean it replaces the keyword, that means after
SubWCRev ran, the keyword is gone. And that means you couldn't run it
again on the same file.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 9 21:55:24 2005