Whats a good online installer that installs vb runtimes ONLY if theyre not present?

I really really hate having to distribute a 1.5mb setup package to install my program when my program is only 30kb, especially because a lot of my clients are on dialup.

Is there an online installer that simply checks if the runtime files are properly installed on a computer, and downloads the vb runtime files ONLY if they are not?

That way I can distribute a 150k app that will connect to the internet and download required files.

Anyone know of a good one?

This has been posted before I think but no answers.. surely after 10+ years of vb (and microsoft not including the runtimes on peoples computers) someone has created such a simple, elegant solution to prevent all vb apps having to be coupled with the runtime files?

I don't believe there is, there wouldn't be much sense either :( it would have to contain all the files and only install the appropriate ones. It would be a pretty big file and people on dial-up (me :() would have to wait hours for it complete.

That's what I was thinking too. What would you hope to gain? There would be complication of detecting just what the user had and if they did not have it they would have to download it anyway. It would be a real pain to maintain. Distribute one package that has everything they need and if need be they could contact you for a CD if the download was too big.

The whole point of an installer is to make sure you have everything you need for the app to work...

well it should be pretty simple..
check if the runtime files exist, if not, download them. naturally the installer would have to be coded in C++ or something so it does not need any runtimes on its own :P

and hell-lord, you are missing the point of the installer entirely. the installer does NOT contain all the files. it just checks if the files are present on the pc, and if they arent, it downloads them.

Well, it's really more than just the runtime files...

Quote:

---

Originally Posted by randem

Well, it's really more than just the runtime files...

---

what do you mean?

It depends on what references and components you are using that will determine what your app really needs. Have you researched this?

Installer Problems

I really cannot understand why people think that my idea is retarded.

Instead of a setup file that is 1.3mb (which includes runtimes + my application), all I want to do is create a setup file which is 150kb (only contains my application) that checks if vb6 runtimes are installed, and if they arent, downloads the runtime files and installs them automatically.

here is something to start with .. http://www.microsoft.com/downloads/d...displaylang=en

Quote:

---

Originally Posted by VaxoP

I really cannot understand why people think that my idea is retarded.

---

Probably because it counts on luck. You do know there are universal VB Runtime files that need to be deployed, correct...

BTW: The amount of effort dedicated to attempting to find out what they have on their computer isn't worth just deploying the things needed... In the end you may force them to download the external installs anyway...:(

The last thing you want is for the customer to have to think...:p

Quote:

---

Originally Posted by randem

Probably because it counts on luck. You do know there are universal VB Runtime files that need to be deployed, correct...

BTW: The amount of effort dedicated to attempting to find out what they have on their computer isn't worth just deploying the things needed... In the end you may force them to download the external installs anyway...:(

The last thing you want is for the customer to have to think...:p

---

no it should be a very simple thing.

1) check to see if the 6 vb runtime files are present, and check their version.
2) if the files are not present, or not up to date, download them.

Ok, which VB runtime file are you going to download?

You will also need to kick off an installation of the runtime files and not have the user intervene.

Wat happens on a broken download? They are using dial-up???

Quote:

---

Originally Posted by randem

Ok, which VB runtime file are you going to download?

---

http://www.microsoft.com/downloads/d...displaylang=en
:rolleyes:

You do realize that since MS is stopping support for VB6 you may need to have that file for download from elsewhere. That page may not exist or may be moved.

Quote:

---

Originally Posted by randem

You do realize that since MS is stopping support for VB6 you may need to have that file for download from elsewhere. That page may not exist or may be moved.

---

Yup .. could put it on a website somewhere .. i dont use it, just found it on a google search .. would still need to make a program that doesnt need the Vbruntimes, that would download the file, run it silent, then do everything else like extract your files, etc etc .. sounds like work to me, and another language to learn :D

Could use Vbscript but then still dependant on whether its installed on the system.

The problem he is going to face is the process to check and download the files is going to be larger than having the file in the installer in the first place... Not worth the time and effort if you ask me...

Yep, might as well just code the whole thing in another language, or like said do the setup. Could compress the files individually using something like 7-zip then put them inside the exe, then extract them and decompress them, install and register etc etc ... lots of work though and still need to use a different programming language to begin with.

He could also just put the runtimes on his site, and tell them if they get an error, download from here :D

Could also just create a decent installer package and FORGET ABOUT IT!!!!

Quote:

---

Originally Posted by randem

Could also just create a decent installer package and FORGET ABOUT IT!!!!

---

I have coded an installer in vb6 works great, but i cant make my own self-extracting exe to extract the setup files and then run the setup. Do you have a vb6 program that can make a self-extracting exe and keep the paths inside.

Quote:

---

Originally Posted by chris1990

I have coded an installer in vb6 works great

---

Erm.. do you realise that you will have to install your setup program before you can run it? :eek:
(and thus have two installs to get one program working)

Evidently he never read the link I posted... Ignoring information is the key to failure...

What in the hell

I have seen DOZENS of applications where the setup file is like 20kb and that setup file then downloads all the neccessary components from the internet during install.

What is the big deal here?

I have a 150kb setup.exe file which I distribute to everyone. This setup.exe is made in C or something where external runtimes are not required to run. The setup.exe checks the SIX (yes there are only 6) visual basic runtime files on a clients computer, and if they do not exist, or if the version is outdated, the setup.exe downloads the runtimes from the internet.

Let me try to dumb it down even further. There is one setup.exe file. It is not 2mb big, it is not 10mb big, it does not contain the vb6 runtimes, it only contains my application, it is 150kb big. There are 2 scenarios. 1) Client has the vb runtimes installed. 2) Client does not have the runtimes.

Scenario 1) The setup.exe installs my application (which is 40kb) and exits. Total bandwidth consumed: 150kb.

Scenario 2) The setup.exe sees the runtimes are not properly present, it downloads the 1mb runtimes and installs them, along with my application. Total bandwidth consumed: 1.15 Mb.

Considering that 70% of people have the runtimes already, the bandwidth required on 1000 installs are:
(700 * .15) + (300 * 1.15) = 450MB - using my method.
Using the (very stupid) method of including all runtimes already in the setup.exe, bandwidth use is 1000 * 1.15 = 1150MB.

Please tell me why in gods name this is difficult.

Quote:

---

Originally Posted by VaxoP

Considering that 70% of people have the runtimes already.

---

70%? 100% of my users have them installed. If one or two deleted them they need to be publicly humiliated. :D

Moved.

Quote:

---

Originally Posted by MartinLiss

Moved.

---

noooooooooooo now ill never get a response :P

Yes, That is fine but you count on 100% of your users having the internet to install the app. Just suppose they want to install on a computer that is not connected to the internet. Limiting the user who can use the app limits the exposure of the app.

Plus if you have such success installing your app... Why the post here????

Quote:

---

Originally Posted by randem

Yes, That is fine but you count on 100% of your users having the internet to install the app. Just suppose they want to install on a computer that is not connected to the internet. Limiting the user who can use the app limits the exposure of the app.

Plus if you have such success installing your app... Why the post here????

---

Thats the main problem right there. :D
Unless his app is an internet app ..?

My program is an internet app =)

What do you mean an internet app? It's coded in VB?

http://www.vbforums.com/showthread.p...71#post3025871