This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Assembly version in output MSI file name
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 02, 2011
05:45 AM
Assembly version in output MSI file name
Hi there,
I'm using InstallShield 2010 to build a C# .NET project. We're moving over to InstallShield having used WiX and Nant to build our installers until now.
One nice thing we do in WiX/Nant is include our .NET's assembly number in the file name of the MSI that the build creates. We do this by compiling the code in Nant, examining it using Nant's getassemblyname function to get the version, and then passing that to light.exe to build the MSI:
This means by executing a single Nant script via CC.NET, we end up with an MSI called MyProduct_1.0.1.msi, which is what I want to end up doing with InstallShield. Currently I can only get it to create MyProduct.msi and then I have to manually change the version number.
Can anyone point me in the direction of how to do this this using InstallShield please?
Tom
I'm using InstallShield 2010 to build a C# .NET project. We're moving over to InstallShield having used WiX and Nant to build our installers until now.
One nice thing we do in WiX/Nant is include our .NET's assembly number in the file name of the MSI that the build creates. We do this by compiling the code in Nant, examining it using Nant's getassemblyname function to get the version, and then passing that to light.exe to build the MSI:
light.exe MyProduct_1.0.1.msi MyProduct.wixobj
This means by executing a single Nant script via CC.NET, we end up with an MSI called MyProduct_1.0.1.msi, which is what I want to end up doing with InstallShield. Currently I can only get it to create MyProduct.msi and then I have to manually change the version number.
Can anyone point me in the direction of how to do this this using InstallShield please?
Tom
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 02, 2011
08:28 AM
You might try using the InstallShield automation object and dynamically build your project that way. We have an automation program written in .Net where we take existing projects, open them, update component, reset the properties, and build the package. This works pretty well for us.