On Mon, May 18, 2009 at 9:59 AM, Nick Gilbert <nick_at_x-rm.com> wrote:
> Stefan Küng wrote:
> > Seems VS doesn't recognize that the version.cs file has been modified?
> > Does this also happen if you do a rebuild instead of just a build?
> > Do you have the harddrive write cache enabled?
> > Maybe adding a sleep() after calling SubWCRev would help?
> >
> > Just some thoughts about what to try - I don't really know why this
> > happens...
> >
> > Stefan
> >
>
> I've done some more testing and the behaviour is very odd. I introduced
> a deliberate compile error into the version.in.cs file and the compiler
> does not recognise the error until the second compile, proving that's
> seeing an old version of the source at compile time. I think as you
> suspect, it's a write-caching problem and csc.exe is somehow able to see
> the old version of the file, even though SubWCRev has successfully
> modified the file and exited. I cannot work out how to add more than
> one thing to the prebuild event though - it seems to go wrong whatever I
> put in as the second line. I'll try and figure it out.
>
> Nick
>
> ------------------------------------------------------
>
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2297913
>
> To unsubscribe from this discussion, e-mail: [
> dev-unsubscribe_at_tortoisesvn.tigris.org].
>
Visual Studio evaluates dependencies _before_ the pre-build actions. You'll
need to push the code that updates Version.cs into a macro, rather than a
build action. We have the same problem in our C++ projects (we generate
Version.h2 from Version.h).
Cheers,
Roger.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2297971
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-18 11:08:35 CEST