I don't like internet installs because they depend on the reliability of the server at all times. Nobody can mirror your files if the install script always looks in the same place - and what if you change web hosts? Ugh.
Originally posted by polaughlin
I think it would be great for VB applications that would need runtimes/ocx's/etc. This way, you could have one installer download and then when the user installs it, if they need any of the required files, they can download them.
Or you could do what I've done, and test for the VB runtime files and re-direct the user to download something else if they don't exist:
IfFileExists "$SYSDIR\msvbvm60.dll" 0 5
IfFileExists "$SYSDIR\mscomctl.ocx" 0 4
IfFileExists "$SYSDIR\mscomct2.ocx" 0 3
IfFileExists "$SYSDIR\comdlg32.ocx" 0 2
IfFileExists "$SYSDIR\tabctl32.ocx" 0 1
MessageBox MB_YESNO "You are missing support files. Download them now?" IDNO 1
ExecShell "" "http://path.to/download/vbruntime.exe"