Mscomct2 Cab Installer

Installing Common Controls Hi all, I have little experience on installers. I'm doing one with InnoSetup. The PDW has given the dependencies list for my app, but for example it places some of them in Windows (others in.PDWizard Redist): C: Windows SysWOW64 Mscomctl.ocx -> v 6.1.98.34 - 2/05/2012 Since from my IDE developing and then the compiled.exe, they both use the DLLs-OCXs versions from my OS. Therefore, my question is if you should deploy the OS-DLLs or the ones coming in VBSP6 (eg Mscomctl.ocx -> 6.1.97.82.

From what I've read I think you should not use from my own HD. How to avoid the DLL hell? One issue is that even the VB6 Service Packs do not take care of updating the PDW's VB6DEP.INI file. There is a reason for that: depending on what OS you are targeting VB6DEP.INI can be different. One of the more important things in that file is a list of files that should not be packaged and deployed. This can be because a file is not legally redistributable, but more often it is because the file has changed status to a protected file already included in Windows or because the file (usually a DLL or OCX) comes in differenet flavors tailored to work on a specific version of Windows. To update your (set of, one per OS target) VB6DEP.INI files means keeping up with every MS KB article relating to VB6 (and in many cases Windows) since 1998.

Re-Install the application that requires MSCOMCT2.OCX. Update the application to the latest version. Install any available Windows updates. Download and install.

A second issue is that because of such changes and code tailoring you should strongly avoid packaging copies of libraries taken from the live system you develop on. The PDW can handle this automatically by checking its Redist folder. This is where the developer is supposed to place OS-neutral redistributable versions of libraries to be deployed. So that's one more point of ongoing maintenance.

I was in the Czech Republic. Vcds 12120 rus dlya kitajskogo shnurka. Hey fuck people fuck epta tired from the road.

If you use some other packaging tool instead of the PDW, you have to do more or less the same thing but it tends to be a far more manual process. This need for PDW maintenance (and multiple profiles per target) is one of the reasons why Microsoft released Visual Studio 6.0 Installer (VSI) as a free replacement (mostly) for the creaky PDW. Windows Installer was still new and the VS 6.0 Installer tools was not ready yet when VS/VB6 shipped. Using this allowed Microsoft to provide merge modules for the libraries that shipped as part of the VB6 package (DLLs and OCXs). These merge modules contain embedded rules about when to deploy and when not to based on the target OS during installation. So instead of creating one PDW setup package for Win95 & NT4, another for Win98 & WinMe, another for Win2K, another for WinXP. You can create just one MSI package and be done.

While you can't legally obtain VSI anymore (Microsoft removed the downloads a few years back, all other sources of those files are considered pirated copies and might contain malware anyway). They do still update the standard when required. If you are not using Windows Installer technology (i.e. VSI or a similar 3rd party tool) then merge modules do you no direct good. However you can download them and extract them to get redist versions to keep in your own PDW Redist folder.

You can do the same thing for some random legacy packager too, but many of them have no direct concept of a Redist folder so you might have to fiddle with 'scripts' manually to make them 'pull' from there instead of the live system. As for avoiding DLL Hell, well. Good luck doing that by using 'the No-No setup.' I find that I have had to do far more cleaning up of messes caused by a 3rd party application somebody used that on than anything else.