Running subwcrev from Visual Studio Build Events

[jd...@jdege.visi.com]

I'd thought it would be trivial to add updating version numbers to the
automated build process, in Visual Studio 2005, by adding a call to
subwcrev to the project's Build Events.

It's not working.

I'm trying:

d:\tools\TortoiseSVN\bin\subwcrev . $(ProjectDir)LocalBuildInfo.cs.tpl
$(ProjectDir)LocalBuildInfo.cs

I get an error "subwcrev ... exited with code 6." Which is
ERR_SVN_ERR, which doesn't tell me much.

The error message includes the expanded command line, and that
expanded command line, cut and pasted into a console, runs without
error.

Any ideas as to what could be causing the problem?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-un...@tortoisesvn.tigris.org
For additional commands, e-mail: users...@tortoisesvn.tigris.org

[Stefan Küng]

jd...@korterra.com wrote:
> I'd thought it would be trivial to add updating version numbers to the
> automated build process, in Visual Studio 2005, by adding a call to
> subwcrev to the project's Build Events.
>
> It's not working.
>
> I'm trying:
>
> d:\tools\TortoiseSVN\bin\subwcrev . $(ProjectDir)LocalBuildInfo.cs.tpl
> $(ProjectDir)LocalBuildInfo.cs
>
> I get an error "subwcrev ... exited with code 6." Which is
> ERR_SVN_ERR, which doesn't tell me much.

The exact subversion error is printed on stdout.

But you call SubWCRev with '.' as the first argument. My guess would be
that the current directory is not really defined in a VS build event.
Use e.g. $(SolutionDir) instead.

And make sure that paths which have spaces in them are placed between
quotes!

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

[jd...@jdege.visi.com]

On Jun 6, 3:33 pm, Stefan Küng <tortoise...@gmail.com> wrote:
>
> > I get an error "subwcrev ... exited with code 6." Which is
> > ERR_SVN_ERR, which doesn't tell me much.

> But you call SubWCRev with '.' as the first argument. My guess would be

> that the current directory is not really defined in a VS build event.
> Use e.g. $(SolutionDir) instead.

That does seem to have been the problem, thanks.