Audience: Install Developers, Beginner, Windows Installer (MSI) Knowledge
This is the introduction to a three part series that demonstrates how to use C++ in a Windows Installer Custom Action.
Windows Installer Actions:
Every task the Windows Installer performs is called an action. Actions are equivalent to what common programming languages refer to as functions, methods or procedures.
There are over 70 Standard Windows Installer Actions. http://msdn2.microsoft.com/en-us/library/aa372022(VS.85).aspx
To extend the standard functionality, use a Custom Action.
There are over 70 Standard Windows Installer Actions. http://msdn2.microsoft.com/en-us/library/aa372022(VS.85).aspx
To extend the standard functionality, use a Custom Action.
Custom Actions:
Setup authors can write their own actions (Custom Actions), to extend the Windows Installer’s default functionality.
There are several types of Custom Actions. http://msdn2.microsoft.com/en-us/library/aa368066(VS.85).aspx
This article will deal specifically with using a .dll though a custom action. (Type 1 or Type 17).
There are several types of Custom Actions. http://msdn2.microsoft.com/en-us/library/aa368066(VS.85).aspx
This article will deal specifically with using a .dll though a custom action. (Type 1 or Type 17).
Windows Installer Dll
Even if you are using InstallScript in a basic MSI project, behind the scenes a .dll is being called. I prefer to skip InstallScript all together, and go for C++.
Not that there is anything wrong with InstallScript. It has just been my experience that making your own .dll is much faster, more portable, and you have more options as to what can be done.
This article will show you how to get up and running. Part 1 >
Not that there is anything wrong with InstallScript. It has just been my experience that making your own .dll is much faster, more portable, and you have more options as to what can be done.
This article will show you how to get up and running. Part 1 >
No comments:
Post a Comment