> "Stefan Küng" <tortoisesvn@gmail.com> wrote on 05/23/2006 06:36:44 AM:
> > On 5/23/06, Chris.Stratmann@blum.com <Chris.Stratmann@blum.com> wrote:
> > Ok...Um...I am doing something a little different than what
other
> > programmers are doing. I am guessing you get questions regarding the
> > resource (rc) file in a C++ project and how to change the strings in
this
> > file before a final build is done so the resulting executable contains
the
> > proper strings. I understand this, but my situation is a little just
> > slightly different.
> > I need to change the version number and add in "Other Version
> > Information" on these exe's and dll's (This is located on the Version
tab
> > can be found in the properties of the executable). The reason being
is that
>
> That's exactly the information contained in the *.rc file of a
> project. Those are the version resources of an executable (exe, dll).
>
> > I would like to look at the version number to find out what repository
> > version number this executable is without actually running it. This
is
> > possible with a little manipulation of the following
> > project...http://www.codeproject.com/library/VerInfoLib.asp
> > I figured out a solution to my own problem. In Microsoft
Visual
> > Studios there is a post-build option which allows my to run scripts
and
> > executables after building an exe or dll. Therefore I just hooked my
> > program that changing the version number into the post-build and
manually
> > retrieve the version number out of the .svn\entries file to write my
new
> > version number on my exe or dll.
>
> Why do you want to modify the version string of your own executable
> *after* the build? You can do the same before the build, and the build
> will then automatically have the correct version info string.
> TortoiseSVN does the very same thing:
> we have the version information not just in our version.in/version.h
> header file, but the defines in that header file are also used in the
> *.rc2 file (included in the main *.rc file).
> That way, the version info is accurate after a build, without the need
> to modify the executable file after the build.
>
> Stefan
Yes you are correct that the *.rc file does change the .exe files version
number......But it is the "Other Version Information" that is also very
important. My final goal is to have an executable with not only its
repository version number but also a list of every dll and every dll's SVN
version number contained in the "Other Version Information" on that
executable. I have about 15 executables and about 20-30 dlls running. If
I wanted to do a rollback on an executable I have to also rollback its
dlls. I have no automated way of knowing which dlls relate to an
executable and their (dlls) SVN version number. Sure I could make a chart
and fill it out with which version number of dll relate to executable but
if it can be automated then why not. Now I put all this information on an
executables version tab through a somewhat complicated process.
To answer your response even further as to why "after" and not "before" is
because I am a lazy programmer, and I take the easy road which may not be
best road. There are two possibilities here. I could either have a
program to modify the .rc file using the "Pre-Link" option in Visual
Studios or have a program to modify the exe using the "Post-Build" option
in Visual Studios. Since modifying an exe using the "Post-Build" is
already complete and working then I am going to take that road because it
requires less programming.
Chris
Received on Tue May 23 13:39:55 2006