The OnMaintUI() and OnUpdateUI() do this for you unless you've overrode them or OnShowUI(). Use can see how they do it by using the little toolbar that sits above the script you are writing in the Installscript section... Also you'll need to use FeatureSelectNew() in order to select any new features that you've added that were not in the previous installation. FeatureSelectNew( MEDIA, TRUE ); if (ADDREMOVE) then FeatureUpdate(""); else FeatureReinstall(); endif; You can use the code in OnUpdateUI() to physically remove old files and then install the newer ones for a complete install. In the Features/Components section you can also specify in the Overwrite properties under the General section how you want to overwrite the existing files. PS. A.I. is one of my favorite movies and your username made my Friday! ... View more

... I completely missed that. Thanks! I am completely in the InstallScript realm. And honestly I do not want to create a script that parses a particular file to switch versions. Would I be able to make use of a public property value from command line? I assume from this post I can. Really the only reason I was using the Build tab is for debugging. ... View more

What do you mean by: I run the risk they get out of sync... And if it matters I forgot a step. In the first one, there are 2 features one labeled x32 and the other x64 but they are linked to the same component whereas the second one is about 2 components (labeled x32 and x64) but linked to the same physical file path. In my install the file isn't dependent on the system so I can place it where ever. There isn't any real syncing unless you the files in the component are structurely different or you are adding file after that component. I guess I'm a little confused on what you are trying to accomplish with reducing the number of components. One of my installers has over 35 components (I think I'm at like 40+ right now). ... View more

If what I'm understanding you want the component to install in both the 32bit directory and the 64bit one, right? You can always let it install in the 32bit one and if the system is 64bit copy the file(s) into the 64bit one. Just add a Custom Action or add the "Installed(yourComponent)" handler to your script or add one after the install in OnFirstUIAfter(). I did something similar for some files in the System32 directory: [LIST=6] Create a parent feature. Create a feature and name it "xxxx32bit" or whatever under that parent one. Create a feature and name it "xxxx64bit" or whatever under that parent one. Create your component. Link that component in both the "xxxx32bit" and "xxxx64bit" feature. In your code (I'm using InstallScript) create a switch that turns the "32bit" and the "64bit" features on or off based on the OS. or [LIST=5] Create a parent feature. Create a component and name it "xxxx32bit" or whatever. Create a component and name it "xxxx64bit" or whatever. Link that component in both the "xxxx32bit" and "xxxx64bit" feature. In your code (I'm using InstallScript) switch the install path that turns the based on the OS. I'm using InstallScript so you'll have to either add some script or make a custom action or some such nonsense (lol). This way you only need that one component. Since the files I'm using are not dependent on the OS (well the file itself but the DLLs it uses are) I only created duplicate components... ... View more

So I stumbled upon OnShowUI(). I feel like a god now. Overriding OnShowUI() will give me full control over the installation. Now I do not have to rely on IS to throw these events in order to deal with them. Now I only need to figure out how to determine if this execution is a first-time installation, Add/Remove call to repair or uninstallation or a cmdline Uninstallation... This helps me suppress unwanted dialog and simulate a silent install/uninstall for when embedding this installer within another and still be able to pop-up error messages (as "/s" will suppress ALL dialogs even error messages). I will update soon for prosperity... ... View more

Somebody asked the same question shortly after yours. I posted my response from that post but the short answer is no and the long is answer is yes. It's easy to do but you will have to fiddle for a few minutes before you get it perfect. And it may only work in certain places and they may have closed that loop hole in the newer version (haven't yet updated to 2012). Is there anyway I can control it's position, or appearance? In 2010 in some dialogs it's a text field that can be deleted but then there is blank line the width of the string where you can't place anything in which is attached to the bottom of the dialog. The way I got past it on the SdFinish and sdWelcomeMaint was to delete the text, and add my text field where their's appeared. If you move the bottom edge of the dialog up and down you will see you text field get covered up by an invisible line. Bring your text to the front and save immediately. You may have to move another field in order to save but if you do it right you can cover their inserted text... Works for me in those specific dialogs. Other may be different or 'fixed'. Hope this helps. Again hope this helps! ... View more

Is there anyway I can control it's position, or appearance? In 2010 in some dialogs it's a text field that can be deleted but then there is blank line the width of the string where you can't place anything in which is attached to the bottom of the dialog. The way I got past it on the SdFinish and sdWelcomeMaint was to delete the text, and add my text field where their's appeared. If you move the bottom edge of the dialog up and down you will see you text field get covered up by an invisible line. Bring your text to the front and save immediately. You may have to move another field in order to save but if you do it right you can cover their inserted text... Works for me in those specific dialogs. Other may be different or 'fixed'. Hope this helps. ... View more

Are you installing over a network? Is your installer a Installscript, Installscript MSI, or pure MSI project? I've had issues with people installing over a local network and they either lose connection or there's a hiccup. Not sure if this is the same issue. If I'm not mistaken, there is a switch that will tell the *.exe to cache unpacked installer locally. If it will help I can look it up. I've noticed that sometimes images won't appear during installation or uninstallation when launching the *.exe from a networked location (mapped drive or network address). Certain cached files won't work over a network. ... View more

From the hlep manual (just found): Error code: -6653 A feature in the setup contains more than 800 components. There is a maximum limit of 1600 components per feature using Windows NT/Windows 2000 and a maximum limit of 800 components per feature using Windows 95 and Windows 98. So there is a limit but I literally have 50 features (never more than 3 deep) and 66 components. So it looks like I'm nowhere near the Feature Limitation. Also found a listing of (un)documented limitations of MSI but I'm not sure if all of these pretain to InstallScript projects too. I've still not found any original threads or postings about this issue. I do not believe this is something isolates nor something I 100% introduced since I built this from the ground up in 2010. Any help, hack, or even someone who has experienced this will greatly help me (or at least not drive me to drink, lol). ... View more

Not sure. I don't have access to it right now but it shouldn't matter too much. I'm just trying to run a query on a user's computer (no remote/server/etc installation just machine to machine) and parse the return using InstallScript. I'm looking for a simple way to execute the query in script. I didn't find any simple tuturials or examples on how to do this (unless I completely missed something). ... View more

I realize that I left out division but removing "*" leaves math operators unstylized. Is there a code for both/either of those such as one the one of "&" (being "&")? I like having the math operators colored. ... View more