Community Forums
Page 1 of 2 12 LastLast
Results 1 to 5 of 6

Thread: SABLD ProductVersion and MSBUILD

  1. #1
    Join Date
    Jul 2003
    Location
    Austin, TX
    Posts
    4,430

    SABLD ProductVersion and MSBUILD

    I was reading there is a new command line switch to pass in ProductVersion as part of the build. Is this supported by the MSBuild task? I don't have VisualStudio installed on my clean machine with IS2008 so I can't tell what changes were made to the ISPROJ files.

    Currently I have a custom MSBuild Task written in C# that I use to override the BeforeCompile target. The task updates the IS XML before building the solution. It would be nice to just define a property with the version number and build the solution without any additional plumbing.
    Christopher Painter
    ISWIX, LLC.
    Visit iswix.com for contact information

  2. #2
    MichaelU's Avatar
    MichaelU is offline InstallShield Software Engineer
    Join Date
    Jan 2004
    Location
    Schaumburg, IL
    Posts
    4,683
    It doesn't look like we have MSBuild support for setting/overriding the ProductVersion yet, but it would be an obvious addition (and hopefully even easy to implement). I've recorded this as IOC-000058042. Thanks for the request!
    Last edited by MichaelU; 03-13-2007 at 10:09 AM.
    Michael Urman - Staff Software Engineer - Flexera Software: InstallShield Team

  3. #3
    MichaelU's Avatar
    MichaelU is offline InstallShield Software Engineer
    Join Date
    Jan 2004
    Location
    Schaumburg, IL
    Posts
    4,683
    Here's an early drop of this before I've even let QA get their hands on it. If you're curious and want to give it a try, you can drop this file in Program Files\MSBuild\Macrovision\IS2008 (or use it wherever's convenient for you). It adds a new string property to the task with name ProductVersion. Let me know if you have any problems with it; I plan to smoketest it tomorrow because I don't have any convenient MSBuild scripts around.
    Attached Files Attached Files
    Michael Urman - Staff Software Engineer - Flexera Software: InstallShield Team

  4. #4
    Join Date
    Jul 2003
    Location
    Austin, TX
    Posts
    4,430
    Sorry, I've been too swamped to try to test this. But still, I have another requirement suggestion.... I've had use cases in the past where I don't have enough control over the build output ( third party binaries in some cases ) enough to enforce the component rules. In these scenarios I must treat every build as a major upgrade to make sure that upgrades would work.

    It would be nice to have a mechanism in the msbuild and sabld to set a flag telling it to generate a new ProductCode just like the way it'll generate a new PackageCode.
    Christopher Painter
    ISWIX, LLC.
    Visit iswix.com for contact information

  5. #5
    Join Date
    Nov 2001
    Location
    Clearwater, FL
    Posts
    213

    I need this also

    Quote Originally Posted by Christopher Painter View Post
    It would be nice to have a mechanism in the msbuild and sabld to set a flag telling it to generate a new ProductCode just like the way it'll generate a new PackageCode.
    I have had to do the same thing. For several of my products the dev manager decided that every upgrade should be a Major Upgrade.

    I would use this feature if you had it.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •