[RESOLVED] OCX files.

Hi,

Is there a way to include/install ocx files like :

richtx32.ocx(rich text box)
mswinsock.ocx
skin ocx files

As it can get quite annoyning when all placed in the folder with the app, and even then somtimes it doesen't work. Also when you are using skin with a ocx file even tho the skin ocx file is in the folder, it makes it alot bigger also.

cheers

If you build distribution package using whatever utility you might have all components used in your project (ocx, dll) will be automatically included.
Try using Package & Deployment Wizard that comes shipped with VB. There is also INNO, etc...

Ocx files should go in the System32 folder from an installation package like RB mentioned.

See the Application Deployment forums FAQ for other packagers and tips.

Thread Moved

Quote:

---

Originally Posted by RobDog888

Ocx files should go in the System32 folder from an installation package like RB mentioned.

---

This is true for the vast majority of OCXs and DLLs. There are exceptions:

• Component libraries that YOU create and provide that are shared among applications YOU provide. These go under %ProgramFiles%\Common Files\{company}\{product suite}
• Component files YOU create and provide that are only used by the one application. These should go into a folder beneath the application's folder, e.g. %Program Files%\{company}\{application}\{component folder name}

Other system components or 3rd party components that might be generally used (i.e. not created by YOU for specific use) should go into System32. Some component vendors also use Common Files which is fine but the vendor should be providing guidance, usually in the form of a .DEP file that comes with the component library file:

FudgeMaster.ocx
FudgeMaster.dep

Those .DEP files contain guidance to packaging software: INFO: How Setup Wizard and PDW Use Dependency Files.

Ok cheers for the info guys, sorted.

Quote:

---

Originally Posted by dilettante

This is true for the vast majority of OCXs and DLLs. There are exceptions:

• Component libraries that YOU create and provide that are shared among applications YOU provide. These go under %ProgramFiles%\Common Files\{company}\{product suite}
• Component files YOU create and provide that are only used by the one application. These should go into a folder beneath the application's folder, e.g. %Program Files%\{company}\{application}\{component folder name}

---

Although it's true but also not necesarily required - destination fiolder can be changed and most (if not all) utilities allow that.

It depends on how you want your app configured. Some apps keep everything in a local folder so its a self contained single folder install. This is probably not the best design but there are many variations each with their own pros and cons.

I used Inno, seemed ok, first time I tryed it it worked, then i recompiled another but added a ocx skin file which was needed for app, it said all my other files wernt registered like I haden't included them in installiation, i retryed 2 more times and it worked, fishy.

I used the wizard instead of typing out the script.