It's "NOT Installed" with a capital I as a condition. Have you logged your installation? also your custom action types are wrong - they should both be "Path referencing a directory" I strongly recommend doing some more learning on Custom Actions. Even the build-in help is good. ... View more

I see. If you use "Path referencing a directory" as your EXE type custom action you will need two custom actions for this: - one that you call during Install (set condition NOT Installed) with the -s parameter before "After InstallFinalize" - one that you call during Uninstall (set condition REMOVE="ALL") with the -u parameter anywhere between "After InstallValidate" and "After RemoveFiles" There are a few ways to Install a virtual printer through scripts - just google for it. If you still want to use your "install exe" method I would recommend using the "Stored in Binary table" custom action type. In this way you don't have to install the "install exe" file with your MSI. ... View more

There is a way to pupulate the combo box with the values from your XML files. The following article will show you how to access the database at run time: www.acresso.com/webdocuments/PDF/msiaccess.pdf. basically you need to create a VBscript to read the attribute values of your elements into an array and then put each item into the ComboBox table. ... View more

tell us a bit more: - what kind of project is it? - what do you need to accomplish with the custom action? - when do you sequence it? ... View more

the user profile is set by setAllUsersProfile2K or SetAllUsersProfileNT, custom actions that run in the UI sequence. ... View more

you need to create an Autorun.inf file and place it on the root of the CD. this article will explain you how to create the Autorun.inf file: http://support.microsoft.com/kb/818804 ... View more

you can use MSIUSEREALADMINDETECTION to check if the user has administrative rights. http://msdn.microsoft.com/en-us/library/aa816403(VS.85).aspx ... View more

why don't you set your INSTALLDIR depending on conditions? use a "Set Directory" custom action. ... View more

In General Information you set the "ProductVersion" property of the MSI. Setup.exe is nothing but a bootstrapper that launches your installation with prerequisites, properties, etc. To change the File Version of the Setup.exe you need to open it with Visual Studio and navigate to Version node. Peter ... View more

First you need to decide which is the best place to store your user data depending wether is shared among other users or just for the current user. This document will tell you more about that: http://sharepoint.microsoft.com/innovateon/vistadeveloper/Developer%20Documents/UAC%20Development%20Requirements.doc Then you can make use of FOLDER_LOCAL_APPDATA or FOLDER_COMMON_APPDATA special folders. Peter ... View more

Go to your dialog under Dialogs/All Dialogs, create your edit box, associate the desired property and give it a significant name. Then go to Behavior, slect your edit box and click on the Conditions tab; create an Enable action and a Disable action and assign the desired conditions for them. This will Enable / Disable your edit box based on your conditions. PS: you can take as example the Next button on the LicenseAgreement dialog. ... View more

can you tell us what kind of project you work on? ... View more

try this: mt.exe -manifest "setup.exe.manifest" -outputresource:"setup.exe;#1" ... View more

this is a good place to start from: http://msdn.microsoft.com/en-us/magazine/cc163899.aspx ... View more

You mean like in the installer for SQL Server Express? That's a bootstrapper created with Visual Studio. ... View more