Hi,
What I meant was that NO resources had the "Make Key Member" option available to it, including files (the ones of interest to me were executables and DLL's, which as far as I know, are files.)
Please note that Advanced Installer generates the components according to the Windows Installer recommendations. Therefore, a new component is created for every .exe, .dll, and .ocx file. Also, these files are designated as the key path files (or key member) of their components. You can read more about how the components are created here:
http://msdn2.microsoft.com/en-us/librar ... S.85).aspx
Therefore, unless you moved the EXE and DLL resources from their original components, they are already the key members of their components. If this is not the case, can you please send us a screen-shot with the problem to
support at advancedinstaller dot com so we can investigate it?
Your approach to providing "help", referring people to MSI documentation for nearly everything, leads me to believe that I might as well have purchased a good book on MSI for $60, rather than spend $260 for Advanced Installer.
Advanced Installer is a MSI-based installation packages authoring tool. This means that our product uses the Windows Installer technology to create Windows Installer packages. Therefore, an Advanced Installer user may need some basic Windows Installer knowledge before using more complex features.
Basically, Advanced Installer allows you to use the Windows Installer technology in an easier way (through a Graphical User Interface) and gives you more control over the installation package.
At the very least, you should have links to/explanations of relevant MSI topics in your help files, wherever some understanding of those topics is essential.
Since the Microsoft links to their articles chage very often, the links may end up pointing to something else.
This wouldn't be a problem for the User Guide on our website (we would update it), but it would be a problem for users which have older versions of Advanced Installer (their help files would be outdated).
What you fail to understand is that if a user of your product understood all of the MSI topics you keep citing, that user would not need Advanced Installer to begin with.
Please note that in order to create MSI packages which use more complex features (not simply adding some files and registry entries), an user may need to know some basic Windows Installer rules and practices.
Also, Advanced Installer is much easier to use than other tools.
Here is the
Microsoft tutorial for creating a simple installation package:
http://msdn2.microsoft.com/en-us/librar ... S.85).aspx
And here is
our tutorial for a simple installation package (using the same technology):
http://www.advancedinstaller.com/user-g ... imple.html
Self Repair is a HUGELY important topic when it comes to making installation projects, but you totally ignore it in your documentation.
Unfortunately, Windows Installer does not support this feature directly. Since Advanced Installer uses the Windows Installer technology, it doesn't support it directly either.
Therefore, in order to implement this feature you should to use the Windows Installer recommended practices. The easiest way is to use an Advertised shortcut like I explained in my previous post.
Also, a more complex way is to use custom code in your application. This code will verify the integrity of the application files and call some functions in the Windows Installer API when some of the files are missing.
Finally, I would like to specify that the Advanced Installer help and documentation are intended for using Advanced Installer, not for explaining how the Windows Installer technology works. Also, when a licensed (or evaluating) user needs to use some complex Windows Installer features he can always ask our support team on the forum or by mail.
Nevertheless, we appreciate your suggestions about the Advanced Installer documentation and we will try to improve it in the future.
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging