tnand53 wrote: I have 2 features A and B. The A feature needs to go to c:\program files and B needs ro go to C:\program files (x86) on a 64 bit OS. Is it possible.. Can you tell me any way to do it...When i mark a componet 64 bit and build. it gives AMD64 template error .... Bcoz, when ever you mark any component as a 64 bit, you must change the template summary to intel64. when you mark a component as 64bit, the the installer will become a 64bit installer. In the Installation designer -> application data-> files and folders view you can configure the components under the feature A or B to the correct locations. ... View more

tnand53 wrote: Install on c:\programfiles\ on 64 bit. I tried the below and failed. Directory Name: INSTALLDIR Directory Value: [ProgramFiles64Folder]\MyCompany\MyProduct Execution Scheduling: Execute only once Install Exec Sequence: After CostFinalize Install Exec Condition: Not Installed And VersionNT64 And ISReleaseFlags="64bit" My 64-bit Product Configuration has a release flag called 64bit; hence, the ISReleaseFlags="64bit" in my Install Exec Condition. If I have a feature that needs to go in c:\progfiles in not 32 and 6 bit..what should i do. Can release flag only be applied for features? Can we do it on component. Can u explain in detail the step how you achieved the above..where u set the release flags and any other proprty u set..it will be great help. Mark the component as 64bit, if you want to place some files in 64bit prog files folder you must mark atleast one component as 64 bit. ... View more

z_efrati wrote: To make the installer get to ForceReboot I added a condition to InstallValidate to prevent it from executing on uninstall. The reboot really executes, however, when the system goes up again, the uninstallation doesn't resume. A message box appears on screen, saying: "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package." I can see that the keys in the Registry are still there, the service (my service) is still registered, and all the files in the installation folder are still there. The uninstall didn't actually work. What I cannot see any more are the package in C:\WINDOWS\Installer, the relevant key in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer, and the app in Add\Remove Programs. Any suggestions? Hi, I am having the same issue now, did you solved it ?? ... View more

teknix1 wrote: Hi, During the uninstallation of our product a reboot (possibly multiple ones) is required. I was thinking of using the ForceReboot standard action but it just doesn't behave the way I want it. Either after rebooting the installation (not the uninstallation) resumes or I get some strange errors about an installation in progress. I suspect the ForceReboot action is meant to be used during the installation part only. I did try to change my code to reboot during installation instead and that works, but that's not what I want to achieve. Has anybody ever been able to accomplish this? Is there another or better way of doing this? Thanks Nic Did you solved it, i'm facing the same problem now.. ... View more

lordmaxx wrote: Is the restart of the mutual services instant? Perhaps if you make each service a separate component within a feature on the basic MSI, then just expand Advance Settings and choose services you can let windows installer handle the starting and stopping of the service as part of installation and uninstallation. One of my setups uses this functionality and it happens quite seamlessly for install and uninstall. Be sure to set the install and uninstall properties within Control settings so that the services are handled correctly. HI LordMaxx, No the restart of manual services are not instanat, they require a reboot. I cannot do it in way you described, because as i mentioned earlier, i have two services, if one service is stopped another will start it automatically so the only soultion is to set both services to start manually and reboot the computer. then after reboot i can uninstall them easily.. ... View more

Hi John, thank you very much for your reply. When we install our software, it install two services. both will look after each other(i.e., if one service stops another will start automatically.). so at the time of uninstallation, i need to set the two serivices to start manually first, and then reboot the pc, and after the reboot i can continue uninstalling the software easily. I know the location of the services and i'm sure that they will be there at the time of uninstallation. Some one suggested me to use Win32 API functions for accessing and controlling the configuration for services and drivers: OpenSCManager(), OpenService(), QueryServiceConfig(), ChangeServiceConfig(). so can i be able to use these wind32 api's in basic msi project. If yes, please provide me with some examples, if no suggest me an alternative. Thanks for the help once again.. ... View more

loralynne wrote: What I did that works for me was add a Set Directory custom action with the following settings: Directory Name: INSTALLDIR Directory Value: [ProgramFiles64Folder]\MyCompany\MyProduct Execution Scheduling: Execute only once Install Exec Sequence: After CostFinalize Install Exec Condition: Not Installed And VersionNT64 And ISReleaseFlags="64bit" My 64-bit Product Configuration has a release flag called 64bit; hence, the ISReleaseFlags="64bit" in my Install Exec Condition. With this custom action, my 64-bit installer installs to Program Files for both a UI install and a silent install. Thanq loralynne, it helped me alot and saved my time. thanq again ... View more

loralynne wrote: I have both 32-bit components and 64-bit components in my project. My 64-bit release includes both the 32-bit components and the 64-bit components. I have a CA that sets the INSTALLDIR to ProgramFiles64Folder, and it has the condition VersionNT64. I build my 32-bit release, and it runs as expected on a 32-bit machine. When I run it on a 64-bit machine, it executes the CA that sets INSTALLDIR to ProgramFiles64Folder since the condition VersionNT64 is met. However, I don't want this CA to be executed when I run my 32-bit installer on a 64-bit machine. I only want it to be executed when I run my 64-bit installer. Hi, i'm having the same problem. i created a CA to set INSTALLDIR TO ProgFiles64Folder on 64 bit machines but it still pointing to progfiles folder. I created my CA with an installscript, MsiSetProperty(hwnd, INSTALLDIR, ProgFiles64Folder); Am i missing some thing?? Please explain how you created the CA. Thanks in advance... ... View more

this link might help you. http://www.installationdeveloper.com/1632/how-to-run-an-msi-with-elevated-privileges/ ... View more

HI lakshman, i'm having the same issue. Did you solved it somehow, please let me know ... View more