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
- :
- how to specify minimum windows installer version of 3.1
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
‎Oct 24, 2008
08:28 AM
how to specify minimum windows installer version of 3.1
Hi,
This is a follow-up to previous post. I found on microsoft's msdn website, under the PageCount property, that this property is supposed to be set to 301 if I want to require msi 3.1, but installshield says to enter 310!
So which is it - 301 or 310? Anybody know?
Also, what about for patches, if I want to specify minimum of msi 3.1 for patches, do I enter 301 or 310??
Many thanks,
pk
This is a follow-up to previous post. I found on microsoft's msdn website, under the PageCount property, that this property is supposed to be set to 301 if I want to require msi 3.1, but installshield says to enter 310!
So which is it - 301 or 310? Anybody know?
Also, what about for patches, if I want to specify minimum of msi 3.1 for patches, do I enter 301 or 310??
Many thanks,
pk
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 24, 2008
12:15 PM
The correct value for MSI 3.1 is 301. This also applies to patches.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 24, 2008
12:55 PM
Much obliged for the respone.
Regards,
pk
Regards,
pk
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 06, 2009
12:37 AM
THANK YOU! This has solved my issue, after a lot of faffing about!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 12, 2011
10:58 AM
this is still a bug in the InstallShield 2011 help.