Are folks using the VB6 "Common Controls Replacement Project" controls? Any caveats or showstoppers?

I'm considering using the VB6 Common Controls Replacement Project controls and would like to see what other's experiences with them are.

Specifically:

1. What do you n开发者_JAVA技巧eed to distribute with them? (I assume just the .OCX file)
2. Do I need to register the .ocx file or just include in the app directory?
3. Do these controls depend on any other ocx's? (There is mention, for example in the Progress Bar replacement that it is using COMCTL32.DLL but the .DEP file does not list that DLL.
4. Are they at least as robust as the controls they replace?

---

I've used various of the CCRP components in various projects (specifically BrowseDialog, FileDialogs, FolderTreeview and High-Performance Timer) and have had no problems with them. To answer your questions:

1) Just the OCX or dll is required to distribute them. 2) Yes they need to be registered. 3) The controls they depend on will be on every system (comctl32.dll is all of the common windows controls and no GDI app without it). 4) The ones I have used I have never had an incident with. I haven't used all of them, so I can't speak for all of them, but they were always very robust for me.

---

We have several apps that have used the CCRP FolderTreeview successfully for years. We have been seeing very hard to find crashes running on Widows 8, and believe we have isolated them to some strange interaction between the FolderTreeview and Windows Explorer instances open on the same folder.

If this is confirmed, it would suggest that you really don't want to use the CCRP FolderTreeview anymore.

---

As of this time, the CCRP project seems to have been dead for a long time (website copyright is 2004).

However there is a different, living, and apparently successful replacement project which may be useful: http://www.vbforums.com/showthread.php?841929-VB6-ActiveX-CommonControls-%28Replacement-of-the-MS-common-controls%29&p=5129155#post5129155

I have used this in projects and it works well. Note that there are several variants of the VBCCR library including an OCX as well as code which is meant to be compiled into your own program.

---

1-3) The DLLs are presumed to be on every system -- you distribute (and register) the OCX only.

4) What controls do they replace?