Folks,

How can I distribute my app with associated DLLs and data files via
CAB? I am trying to distribute my ActiveX OCX along with the DLLs,
data files and directory structure via cabinet file (.CAB). I looked
at OSD and INF files, but neither seems to handle this kind of
scenario as I'd like. It seems that the .msi would be a better
delivery agent. I would prefer not to install the DLLs into the
%SystemRoot%. Any suggestions?

Thanks
-BEA

It's been a few years (like 10) since I last looked at this, where C++
ActiveX OCX was all the craze, but it looks like Visual Studio (I'm
using 2005 as of this writing) says that Cab Project*1 'Creates a
cabinet file for downloading to a legacy Web browser.'*2 I am hearing
that NSIS*3 is the way it's done these days. Is that true? I hate to
make bad arch decisions, but it looks like I may have done that
already by going with ActiveX OCX instead of the 'good ol app', but I
needed a web based app for windows, natively.

*1 From VS Projects -> Other Project Types
*2 Deployment in Visual Studio, Setup and Deployment Projects
*3 http://nsis.sourceforge.net/Main_Page



On May 23, 5:23*pm, Beagle <beagle...@hotmail.com> wrote: