I'm designing a new MSI installation for a product that allows multiple instances to be installed. Many of the components of the installation are identified by a 2-character code. Among these is an ODBC data source. The name of the data source includes this 2-character code, which is something the user enters during installation. I notice that I cannot use a property name "[MyPropertyName]" as the Name of an ODBC DSN in an InstallShield project. Is there any clean way to allow the ODBC DSN name to be set at runtime? If I were creating hard-wired names for each of my instances, I could create a separate DSN for each hardwired instance name ("Test" and "Production" for example), but we allow the user to specify the name. Am I going to run into more dead-ends as a result of this or is there a way to allow user-specified instance-specific property values?
相关问题
- How does the setup bootstrapper detect if prerequi
- Wix: How can I set, at runtime, the text to be dis
- Mysql-installer showing error : Memoy could not be
- Can ClickOnce or InstallShield setup SQL Server or
- Cancel installation from my custom action
相关文章
- chained msi's/Bootstrapper/prerequisite?
- How to prevent WiX bundle with same UpgradeCode/Ve
- Running msiexec from a service (Local System accou
- Set InstallPath registry key using Visual Studio S
- Looking for a flexible windows installer product w
- Can I use msilib or other Python libraries to extr
- WIX 3.8 msiexec.exe /quiet Error 1603
- Setup Project for Visual Studio
You could either a) skip the ODBC tables in MSI and use the Registry table instead or b) use a custom action to dynamically inject custom rows at install time into the ODBC tables.