OK, so after much trial and error, here's what I did. 1- download ORCA from microsoft. 2- copy ISMsiPkg.itp 3- load up the .itp file in ORCA 4- go through the tables listed here: http://msdn.microsoft.com/en-us/library/aa367767.aspx and edit schema on the 3 tables to change the listed column from i2 to i4. 5- in the _validation table you need to find the table entry for each of the tables you just changed the schema and again change the MaxValue entry. Seems a little silly to have to mod it twice, but you have to. 6- replaced the ISMsiPkg.itp with my edited version. Here's the next issue- any thoughts? Once I did that I could build my project. When I added in all the files (dynamic linkage) it broke signing. When I went through the Release Wizard and unchecked the "Sign Windows Installer Package" box it will build the setup.exe. I verified twice that the only difference is whether I add in the new files. So, on the upside, it works. The downside is that it now takes about two hours to create a setup.exe. Previously it took about 20 minutes. That seems like a pretty crazy increase in time. Previously: ~29k files, 170ish meg setup.exe, ~20 mins to create setup, signed. Now: ~38k files, 220ish meg setup.exe, ~120 mins to create setup, unsigned. ... View more

Any help? This thread has 1100+ views, so people are definitely facing this problem. I can export the tables from the direct editor, but I can't re-import them, as there is a name collision, and I can't drop them to re-import my edited copies. What's the right way to do this? Added bonus- will hand editing these files persist through updates? ... View more

You can do it outside of InstallShield by using reshacker. It's onerous and nice they finally fixed this issue. ... View more

You can change it on a one-time basis in the UI. We increment our build #s with our nightly build, so we wrote a VB script to increment the ISM file in conjunction with our nightly build. If that is what you want to do, check out this documentation: http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/IHelpAutoISWiProject.htm Be aware the documentation is a little old, so you'd want to replace the 12 in this line:Set m_ISWiProject = CreateObject("IswiAuto12.ISWiProject") with 14. See the properties for ProductCode and ProductVersion. ... View more

Is there a step by step tutorial for doing this? In my basic MSI project I don't see how to change the column type in the file menu, and I'm not sure how to open the .itp files in a usable format. ... View more

Anyone have an idea how to get the launch checkbox to actually work? ... View more

We had the same problem and it has not ever been resolved. ... View more

Unfortunately we never found a resolution and were forced to direct all our customers to uninstall the previous version manually. Didn't look good, and doesn't make management happy about Installshield. ... View more

Latest test. I made a fake version 3, changed name, package code, version, product code. version 2->3 upgrades fine, removes v2 from add/remove programs. v1->v3 fails to remove add/remove programs entry. I think there is a bug updating an Installscript MSI install generated in IS2008 to a Basic MSI generated in IS2010. It repeatedly considers itself to be in maintenance mode, but only when upgrading from the v1, not from v2->v3. ... View more

Previously we had a min version specified of 000.000.000, when I added that it behaves the same, but then manual install from add/remove programs breaks. ... View more