Missing ocx file missing dll , when will it stop!

I have made a program that uses msinet.ocx (INET) file transfer , and it works perfectly with mine , i was so happy to finish the project , when i sent it to a friend to test it on his computer , he told me that he didint have the correct ocx's

I am wondering if theres a global ocx or dll all omputers have that i can use to have simular ftp access like winsck or inet.

or do i have to putt a built in ocx registerer in my program?
or can i only have the needed dll's present in the APP.path ?

to make the question simple as possible

how can i make a project to work on all XP computers.

make an installer package, check out inno setup

that is the only way to be sure

Make a installer that will add those ocx and dependancies.

VB comes shipped with Package & Deployment Wizard (aka P&DW) that is very easy to use.
It automatically adds all necessary ocx/dll files used in your project.
However, if you have any additional files (like graphics, mdb, ini, etc...) you will have manually add them all by following simple on screen instruction. You can also specify destination folder for each file.

I dont want my users to be going threw an installation/wizard ,

I have so far made a small program that registers the needed OCX's by reading a INI file.

by the way whats the class name of winsock? [winsck.ocx]

so far i am not sure if this program works since i am allready registered with the needed ocx's so any ideas how i can test this?

Quote:

---

Originally Posted by IQAB

I dont want my users to be going threw an installation/wizard ...

---

Why??? That's the way it works or you're looking for troubles.

no lol , i only preferif my application is ran smoothly and clean , becous ei promised some people to make a good FTP client and one of the rules was that it cant be an installation/setup

maybe a msgbox saying " you do not have 'inet.ocx' installed would you like to install it "
but not a hole wizard , i cant have that

Tough luck I'm afraid... what you are trying to do is basically the same as an installation package would do, the only significant difference is that you will probably miss out one or more requried steps, which will lead to the program not working.

The only way for a VB program to run "smoothly and clean" is for it to be installed before you run it. If you dont want any installation/setup, rewrite your application in a language other than VB.

If you want you can change the installation, so that it doesn't show anything to the user (doesn't ask for installation folder etc). To do this simply modify the project that P&DW uses, which I believe is called Setup1.vbp (I think it is on the VB CD, and not installed by default).

i think i figured out a way to register the needed files , i just used the trusty IEXPRESS.EXE , creates a temp folder and runs the installer , fast and simple.

What does the setup do exactly?
copes files to system32 folder and registers in the REGISTRY , and pretty much it.
exactly what my program does.

I just checked out IExpress, and it sounds like it is an installer for Internet Explorer.. which would be a bit overkill as you are installing much more than needed! (and you are also potentially damaging the users current setup)

What a setup does is basically what you said (also taking into account things like multiple logins for a computer).. but the important thing (in the case of P&DW at least) is that it detects all of the files you require, not just the ones you think you need.

A common one that people miss is the VB runtime files, so their application will only work on machines that already have it installed (for VB6 that means Windows XP or later, anything else is down to luck). Even on machines where it is installed, it may be the wrong version (it may be SP3, whereas your program needs SP6).

All i will be installing/registering is the winsck.ocx , wich is all my program uses at the momment , and im aware that it will not work on below XP, and its not a problem since 80% of all pc's are xp.

How much size does the installer take?

size does matter to me :P

So you aren't bothering with the other files that winsck.ocx itself requires? Oh dear! (it's gonna fail on at least some computers)

..and you don't care that various VB service packs have corrected bugs that will stop your program from working with winsock? If people have the wrong versions of the runtime files (which they could well do even with XP) then your program will have 'random' bugs.


In my experience, the installer for a VB program will generally be about 10 to 15 MB. This does of course depend on what program you are using (P&DW, InnoSetup, ...), and extra files you are including.

15mb is too much.

what do you mean block winsck? there are allot of programs out there that use it like RPG's and ftp clients , why would it be blockeD? if u mean a firewall , its ok theres an [allow ] option.

and i thought in order for winsck to work all u need is the ocx to be registered.

Moved.

Quote:

---

Originally Posted by IQAB

15mb is too much.

---

You may find that the package for your program is small enough for you, if not then dont write programs in VB!

Quote:

---

what do you mean block winsck?

---

I didn't say block winsock - I said that your program may not be able to work with it. There have been many bugs in the VB runtime files which (sometimes) cause odd faults with 'external' controls/DLLs.. I'm sure that at least one of the service packs corrected issues with WinSock.

The only way to be sure it will work is to install runtime files from a recent service pack.

Quote:

---

and i thought in order for winsck to work all u need is the ocx to be registered.

---

I think it also requries a few DLL's that the OCX itself uses (an OCX is [very] basically a program in itself), but I'm not sure.

The really big issue with not using and installer is you may finally get your app to work but may destroy other apps ability to work.... Expecially if you are relying on luck!!!