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 validate an InstallScript project for Vista?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Feb 19, 2008
03:36 AM
How to validate an InstallScript project for Vista?
Hello,
I have an InstallScript project migrated from IS 6 to IS 11 and then to IS 14 (IS 2008).
In IS 2008, I cannot use the "Build -> Validate -> Certified for Windows Vista..." menu because my project is not a MSI project.
So what are the other ways to validate my project for Vista, knowing that my setup must also be compatible with Win.2000 and XP?
1) Is there a way to migrate an InstallScript project to a MSI project?
2) If not, must we do the job "manually"?
Thanks in advance
Pascal
I have an InstallScript project migrated from IS 6 to IS 11 and then to IS 14 (IS 2008).
In IS 2008, I cannot use the "Build -> Validate -> Certified for Windows Vista..." menu because my project is not a MSI project.
So what are the other ways to validate my project for Vista, knowing that my setup must also be compatible with Win.2000 and XP?
1) Is there a way to migrate an InstallScript project to a MSI project?
2) If not, must we do the job "manually"?
Thanks in advance
Pascal
(3) Replies
‎Feb 19, 2008
01:08 PM
The build validators you are referencing primarily check table data of MSI files and are thus MSI specific. (They're also implemented in ways tied to the MSI format.) As I recall one of the requirements of the Vista Logo program is to use MSI, so if that's your goal, you will need to verify that requirement and reconsider your packaging strategy.
If instead you are looking for automated assistance aligning your package with the current view of best practices, the ICEs that aren't actually specific to MSI are checking data in your files. As a workaround to check your files, it would probably be easiest to add the files to a very rudimentary MSI install, build, and validate. You could then pay attention to the digital signature, manifest, and obsolete/deprecated API warnings, and ignore others as you saw fit.
If instead you are looking for automated assistance aligning your package with the current view of best practices, the ICEs that aren't actually specific to MSI are checking data in your files. As a workaround to check your files, it would probably be easiest to add the files to a very rudimentary MSI install, build, and validate. You could then pay attention to the digital signature, manifest, and obsolete/deprecated API warnings, and ignore others as you saw fit.
‎Feb 19, 2008
02:18 PM
pinchauret wrote:
Hello,
I have an InstallScript project migrated from IS 6 to IS 11 and then to IS 14 (IS 2008).
In IS 2008, I cannot use the "Build -> Validate -> Certified for Windows Vista..." menu because my project is not a MSI project.
So what are the other ways to validate my project for Vista, knowing that my setup must also be compatible with Win.2000 and XP?
1) Is there a way to migrate an InstallScript project to a MSI project?
2) If not, must we do the job "manually"?
Thanks in advance
Pascal
You may want to start with a repackage to an MSI and work from there.
reg, Henno
‎Feb 21, 2008
09:35 AM
Hello,
Thanks to both of you for your response.
I'm going to create a temporary MSI setup to test my files and will migrate my project to MSI later. 🙂
Bye
Pascal
Thanks to both of you for your response.
I'm going to create a temporary MSI setup to test my files and will migrate my project to MSI later. 🙂
Bye
Pascal