Hi again Moshud,
The thing is, WriteIniValues is not a custom action. It is a standard action, meaning Windows Installer does that action. It is actually responsible for creating the INI file you are configuring from the Files and Folders page.
I read you last post and i believe you are asking me to define a feature with my INI values then either use the search result or my vb script to trigger the installation of this feature to create my INI values. Well, I figured this out before but I thought it would be a wasteful use of features since creating the INI values would be the only action that would fit into this scenario.
Not exactly. I was thinking more of using a component. Features are visible to end-users, meaning they can select them to be installed or not (usually). Components are part of features, they are not visible to end-users and are easier to condition for installation using your search result property.
I have no doubt you've carefully read our guide, however we are exposing a lot of functionality available in Windows Installer. There are things that, even if documented in our user guide, can't fully be understood unless experimented first-hand, which is why we actually recommend users to follow the tutorials there.
Regardless, we're here to help clarify issues and guide our users on the right path
Best regards,
Gabriel
FOLLOW US
Get the latest news in Application Packaging