RE: SubWCRev.exe weirdness when used in website .NET project
From: Oddvar Kloster <okl_at_sintef.no>
Date: Mon, 18 May 2009 13:44:08 +0200
On Mon, May 18, 2009 at 10:33 AM, Nick Gilbert <nick_at_x-rm.com<mailto:nick_at_x-rm.com>> wrote:
At least in C++ projects, Visual C++ compiles the .CPP files into .OBJ files. It will only recompile the .CPP file if it's newer than the .OBJ file. Unfortunately, it checks this _before_ it runs pre-build actions. This means that, if your pre-build action updates the .CPP file, it will be ignored and the older (incorrect) .OBJ file will be used instead.
I assume, based on the description, that something similar's going on with C# files as well -- it's ignoring the .CS file, because it doesn't spot that the pre-build action has modified it. I assume that it only part recompiles the assembly, leaving the "unchanged" files in there from last time.
Now, C# could be completely different, and I could be completely wrong, but I figured that it might be worth your while looking into a pre-build macro, rather than a pre-build action. It's a mess, but it might work.
How about introducing a utiliity project that is a dependency of your main project? This project updates your Version.h (say, in a pre-build action), before your main project checks which files need to recompile.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
This is an archived mail posted to the TortoiseSVN Dev mailing list.