# Additional parameters for Inno Setup

**URL:** https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769
**Category:** Feature Requests
**Created:** [November 21, 2006, 3:56am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769 "2006-11-21T03:56:43Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![boulrik](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/boulrik/32/2793_2.png) [@boulrik](https://www.finalbuilder.com/forums/u/boulrik)
#### Post date: [November 21, 2006, 3:56am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769/1 "2006-11-21T03:56:43Z")

</div>

Is it possible to get additional parameters for the Inno Setup Action? I need this to pass some defines to the setup pre-processor.  
Thanks,  
Ulrik S.

---

<div class="post-metadata">

### Author: ![angus](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/a/b3f665/32.png) [@angus](https://www.finalbuilder.com/forums/u/angus)
#### Post date: [November 21, 2006, 11:41am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769/2 "2006-11-21T11:41:28Z")

</div>

Hi Ulrik,  
  
At the moment we’re limited by the fact that we’re actually calling the Inno DLL, and it doesn’t seem like you can easily pass in defines.  
  
We’ll add a “Inno Command Line” action to the to-do list. In the meantime, you can get the same functionality by using the Execute Program action.  
  
- Angus

---

<div class="post-metadata">

### Author: ![boulrik](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/boulrik/32/2793_2.png) [@boulrik](https://www.finalbuilder.com/forums/u/boulrik)
#### Post date: [November 22, 2006, 11:22am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769/3 "2006-11-22T11:22:32Z")

</div>

No hurry, I’m already using the Execute Program action. But it would be nice with a Inno Command Line action so I can reuse the Inno path from FinalBuilder settings.

---

<div class="post-metadata">

### Author: ![miracle2k](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/miracle2k/32/76_2.png) [@miracle2k](https://www.finalbuilder.com/forums/u/miracle2k)
#### Post date: [March 16, 2007, 6:59am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769/4 "2007-03-16T06:59:16Z")

</div>

I’d be interested in that as well, mainly so I could use the { **param:_ParamName_|_DefaultValue_}** to pass stuff like version numbers etc. to the script.

---

<div class="post-metadata">

### Author: ![angus](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/a/b3f665/32.png) [@angus](https://www.finalbuilder.com/forums/u/angus)
#### Post date: [March 20, 2007, 2:05am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769/5 "2007-03-20T02:05:54Z")

</div>

Hi Michael,  
  
Just for the record, the way that we’re doing the same thing is by having a “template” ISS file with some FinalBuilder variable references in it (ie %VersionNo%.) Then, at build time, we use a Replace Variables action to read the “template” file, replace the variables with their current values, and then write that out to a -new- ISS file which is then built by Inno Setup.  
  
Nevertheless, we’ll look into doing a new command-line-based Inno action in future.  
  
Regards,  
  
Angus

---

<div class="post-metadata">

### Author: ![miracle2k](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/miracle2k/32/76_2.png) [@miracle2k](https://www.finalbuilder.com/forums/u/miracle2k)
#### Post date: [March 22, 2007, 4:59am UTC](https://www.finalbuilder.com/forums/t/additional-parameters-for-inno-setup/3769/6 "2007-03-22T04:59:35Z")

</div>

I considered using a template as well. However, right now I am using InnoSetup with the ISPP extensions, which allows me to pass defines to the script, and that works great.  
  
Also, just to avoid confusion for anyone reading this, I noticed after my previous post that the “/param” option actually applies only to the generated setup itself, NOT the compiler, so that would not have worked anyway.
