«
»

VS .NET 2003 : Pre-Build Script

I spent far too much time today trying to get my Windows Mobile application to try and run a script before building the application. Everything, even MSDN articles told me that the C# IDE could run pre-build scripts, but I couldn’t find them in the properties of the project where it is said they would be. By building a Windows CE application there is lots of little stuff that isn’t supported. But this isn’t really tied to the run-time or other applications. This is the IDE that isn’t behaving the same as documented.

So it looks like I’ll have to run the shell script to update the version manually. This is such a simple thing to do in most development environments. Perhaps even so trivial I’m not seeing the answer, but like I said this isn’t normal Win32 development – the embedded environment seems to have some subtle differences.

I miss make.

This entry was posted on Wednesday, February 8th, 2006 at 7:08 pm and is filed under Software. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

6 Responses to “VS .NET 2003 : Pre-Build Script”

  1. Baron Says:
    February 8th, 2006 at 11:13 pm

    I hate make. C++ pointers are the devil.

  2. Jen Says:
    February 9th, 2006 at 3:18 pm

    I don’t get it
    :o)

  3. Baron Says:
    February 9th, 2006 at 8:51 pm

    Don’t worry about it. Me neither.

  4. Avery Yuen Says:
    February 10th, 2006 at 5:56 pm

    I read the first two or three sentences, at which point my eyes started to glaze over and I gave up trying to get it.

  5. Nesser Says:
    February 11th, 2006 at 12:59 pm

    Anything that is classified as only “Software” is going to be pretty geeky. Reader be warned.

    The basic idea is wanting to embed the exact reveision number of the code in my source control repository into the running application. So if a user in the future says they found a bug I can ask them to read me the version string and know exactly what lines of code are running on their system.

    When someone manually releases version 1.0.1 and then 1.0.2 how do you know the differences between these two running binaries which are now out in the “wild” aka – real world? How many sub-releases took place between those two versions? How many beta testing builds went out? That’s why Microsoft has version numbers like 3.1.4523

    This is probably one of the most important part of any software project. Knowing the state of the running system at any point in time. I don’t know how other software developers live without revision control and the knowledge it brings.

    I posted my windows .bat script for C# on the subversion users mailing list.
    http://svn.haxx.se/users/archive-2006-02/0473.shtml

  6. darryl Says:
    February 14th, 2006 at 11:11 pm

    hmm.. I won’t be programming a windows mobile application anytime soon but that’s interesting… I’m still not hip to this subversion business.. Perhaps i have no need for it at the moment. But I will most likely once I am developing my software for my thesis.

Leave a Reply