Our application consists of several ActiveX controls that run inside of IE and is hosted by an internal webserver. The initial website HTML page has code to load one ActiveX control and application code within that control attempts to download any updated controls. This is currently built in VS 6 and we are trying to migrate to VS 2005. My development platform is XP SP2 and I am using SP1 of VS 2005.
Currenly, the application has an "inf" file for the main ActiveX control that lists the mfc42.dll and msvcrt.dll as dependencies and handles those by running the mfc42.exe installer found at the microsoft website.
Is there a similar mechanism for the VC 8 and MFC 8 equivalents? The INF file looks like the attached. I can change the mfc42.dll and msvcrt.dll to the newer mfc80.dll and msvcr80.dll, but not sure if there is a HTTP link to get the installer for those available? I suppose, worst case, I could deploy the redist exe to our local webserver and reference that instead of a public one from Microsoft?
Tips, hints, suggestions, all welcome.
- Edited by Bill Beacom Friday, August 29, 2008 5:33 PM Code block was a bit wrong
Bill Beacom said: Tips, hints, suggestions, all welcome.My suggestion is very simple: Statically link. If you remove all dependencies entirely you don't even need an INF file. Just download the OCX file directly.
Yes, the control becomes big, but that's because MFC is a poor choice as a framework for a downloadable ActiveX control in the first place. ATL is superior in this regard.