PDA

View Full Version : Migration Issues in InstallShield 2012 Spring.



prasnnakumar
09-06-2012, 07:43 AM
Hello All,

We have migrated our installer from Installshield version 12 to spring 2012 professional edition, since our product migrated to .NET framework 4 & Installshield spring 2012 has support for it.
Following is sequence of action we have performed
• Upgrade Installshield version 12 (Basic MSI project) to Installshield spring
2012 professional edition (Basic MSI project)
• Used Project converters to convert Basic MSI project to Install script MSI
project, since we want to have custom themes for our installer.
• Above Both conversions went well with no hassle.

We have custom dialog boxes to perform various custom operations , following is nature of custom dialog boxes
• Custom dialog box with couple of drop down controls, one drop down
control populates other one.
• Custom dialog box having controls to accept & validate logged In user
credentials.
• Custom dialog box for accepting SQL Server name, SQL Server auth type
(radio button) and based on that the SQL server credentials etc.

After conversion we have observed following things:

1. All custom dialog boxes are lost.
We tried to import the previous custom dialogs into new migrated project
Tried for creating new custom dialog boxes as well.
Please provide best practice for migrating custom dialog boxes even with manual approach.

2.We are getting following error while we build Installshield project using command line arguments
Embedding file D:\Program Files\InstallShield\2012Spring\Redist\Language Independent\x64\ISBEW64.exe into isregsvr.dll
ISDEV : error -1024: File not found. Cannot stream the file into the Binary table

Please provide solution for above errors (#1 & #2).

Thanks,
Prasnnakumar

joshstechnij
09-06-2012, 03:05 PM
Because these project types do not use the same UI, any custom or modified dialogs will need to be recreated in the InstallScript MSI project. Please note that InstallScript MSI projects introduce a large degree of complexity and overhead compared to either Basic MSI or pure InstallScript projects. Depending on the requirements for an installer, we recommend using either Basic MSI or InstallScript projects to simplify the installation as much as possible.

Regarding the -1024 error, is the file D:\Program Files\InstallShield\2012Spring\redist\language independent\x64\ISBEW64.exe present on the machine? If not, you may try repairing the IS 2012 Spring installation to see if that reinstalls this file (it shouldn't be missing though). If the file is not missing, try building this project from the command line builder (iscmdbld.exe) and pass the -v option to create a verbose build log. If possible, attach the verbose log to this thread.