First of all, it's a MessageBox JUST after you run the setup file, or during the setup? Try to select IIS4 and reselect IIS5.1. Maybe for some reason it "stucked" at IIS6. Also take a look at the MSICode Editor (if you have a version that has it enabled), at "Check Application Require...

Sorry,

What' exactly is $SystemDrive# ? It was supposed to be $SystemDrive$ ? It can't be working on XP or 2003 but not on Vista, because that specific command has nothing to do with the OS. It's a simple String Replace command.

Click at "Design" tab , then "Deployment Section"->"Build Settings", check "Debug Build" with Uncompressed Build selected. Rebuild on Uncompressed Build, then run with Debug button.

Well, Pete.. At least you found a solution.. That's something, isn't? [:P]

You have to remove the patch installation from the Add/Remove Progams. It's actually a Windows Installer limitation. If you check "Show Updates" all the .msp files (patches) from your product, will appear below it as a tree. Remove the one you want and try again, it should work this time.

It's very easy to do it yourself also.

Please check the whitepapers about extending the runtimes window.

You can use a trick and make your installer re-launch itself, with the parameter set, if your user doesn't set it. You'll need to check if the $CMDLINE$ variable if it contains the /l parameter and if it doesn't, use Run Program As and one of the variables containg the setup exe (different if it's S...

If the update you don't want to remove the old version and re-install it. You have to change your Product Code, so it will be treated like a new install from Windows Installer. Otherwise, having the same product code, it will find the old product and will update it. But if you have only changed 10 f...

You probably forgot to change the GUID. The new setup detected the old one, removed it and re-installed itself.

During install, you have to write to the registry (or a text file, whatever you want) the $UNINSTALLLINK$ which is the full path where the update wrapper lies. Then you have to resolve from your application what the path is, and launch it, although i don't think it's a good idea to do it like this. ...

OK, here it goes: * New installer: A single self extracting installation that replaces the files * New Install File: The update (version 4) installer with correct WMBs 1) Create a new Installer containing the files to be changed and add a web update reference to your NEW install file (containing the...

I think i understood correct what you want to do, so here it's a solution it might work. You can create a NEW installer, that does not create an ARP entry (not shown in Control Panel/ Add Remove programs) that will REPLACE the files you want and then prompt your users to download the latest web inst...

Alex made a mistake. You cannot call non-native (Win32) dlls from InstallAware. The best to thing to do is create a small .exe file and run it with "Run Program" to validate the xml file and catch it's exit code (for example 2 for success, -1 for failure).

You can run the asp registration .exe no matter if it's already installed or not. It won't affect anything if it's installed, so you don't need to detect anything at all.

Who said he's out of luck? This is exactly why we created this thread.. To send old versions if we still have them in our repository.