MSI database validator

[stampy]

I generated a new, blank, setup from the Win32 Template and when I run theMSI Database Validation tool with the "Display Warnings" checked, I see a number of warnings. There aren't any errors, just warnings -- I'm assuming it is because of (negligible?) IA incompatibilities with MSI?

Any suggestions on how to keep alert for when an "important" warning is flagged (I'm still somewhat new to MSI)? I'm assuming I could provide some build automation that diffs the "known" warnings with any new warnings that might occur following changes to a setup -- for better troubleshooting in times of crisis . Also, any recommendations or suggested resources for analyzing errors and warnings? One reason I ask is a couple of times I've gotten myself into weird build/runtime trouble while playing around with IA and I wasn't sure if it was because something I've done illegally with MSI or illegally with IA; for example, whenever I attempt to run one of my particular setups, I always get an Error dialog: "Could not access network location <yada yada my target dir>" which occurs at the point the "Apply Install" command executes. I reckon it is because of some mistake I've made with IA which I thought I might be able to help troubleshoot with the database validator.

Thanks!

[MichaelNesmith]

Hi Stampy!

The Database Validator validates MSI databases for logo compliancy only. You can safely ignore warnings here as they will not affect your ability to get the Designed/Certified for Windows XP/2003/etc. logo. The only issue will be errors, and you should very rarely - if at all - get those. InstallAware should take care of all that for you - transparently.

As for the error you mentioned. It does seem to be a scripting error. While the database validator might catch some scripting errors, it might miss them as well. The only way to be certain that everything is OK is to test your setups thoroughly.

The network error is most probably an incomplete path that you specified in the script. For instance, lets say you are using the Install Files command, and the destination folder is set to "My Directory". This can raise this error. It needs to be a fully qualified folder, such as "C:\\My Directory". If you use a variable in that field, such as $TARGETDIR$, the variable must contain a fully qualified folder.

Hope this helps!

[stampy]

Ah, that's it. I had a typo (a space char) in front of $TARGETDIR$ of one of my numerous "install files". Tough to spot. Thanks for the help!