> I've made a custom ocx, which amazingly enough seems to work.
> :-0
> I place an instance of it on a form in a std exe project.
> I have registered the ocx via regsvr32.
> the project is now compiled to an exe and I ran dependency walker to check
> for files required since I plan to distribute this to a couple co-workers
> to
> use so I wanted a list of what files I might need to install on their
> machines to let it work.
> I was surprised that the ocx file wasn't among the list.  I was imagining
> I
> was going to have to copy it and register it on any machine using the app.
> Does all that ocx magic just get wrapped up in the exe and magically work?
> So registering a component is just a development phase requirement???
>
> or does dw just not list custom ocx's?

:-)


>
> > the project is now compiled to an exe and I ran dependency
> > walker to check for files required
> > I was surprised that the ocx file wasn't among the list.
>
> Dependency Walter works with native Windows-type
> dependencies; it knows nothing whatever about COM
> components that you might be using.
>
> > I was imagining I was going to have to copy it and register it on
> > any machine using the app.
>
> You will. Or, at least, your Installation Package will.
>
> As a starting point, look at the Package and Deployment Wizard
> - it's basic, to be sure, but it's served me well in the past and /will/
> locate the need for your OCX, /include/ it in the Package and install
> and register it as your end-user installs it.
>
> > Does all that ocx magic just get wrapped up in the exe and magically
> > work?
>
> Nope.
>
> > So registering a component is just a development phase requirement?
>
> Nope.
>
> COM Components /have/ to be registered before you can use them,
> because you access them either by GUID (Early Bound) or ProgID
> (Late Bound), both of which require mapping, via the Registry, into
> the physical location of the DLL.
>
> HTH,
>     Phill  W.
>
>

"Phill. W" <P.A.Ward@o-p-e-n-.-a-c-.-u-k> wrote in message
news:diit4d$8e6$1@yarrow.open.ac.uk...
> "MP" <nospam@Thanks.com> wrote in message
> news:0e43f.74$1A1.64@tornado.rdc-kc.rr.com...
>
>> I've made a custom ocx, which amazingly enough seems to work.
>
> Be surprised; be very, very surprised ... ;-)
>
>> I place an instance of it on a form in a std exe project.
>> I have registered the ocx via regsvr32.
>
> /I'm/ surprised - that it worked that way round.  I'd expect that
> you'd have to register it /before/ you can use it, but anyway ...
>
>> the project is now compiled to an exe and I ran dependency
>> walker to check for files required
>> I was surprised that the ocx file wasn't among the list.
>
> Dependency Walter works with native Windows-type
> dependencies; it knows nothing whatever about COM
> components that you might be using.
>
>> I was imagining I was going to have to copy it and register it on
>> any machine using the app.
>
> You will. Or, at least, your Installation Package will.
>
> As a starting point, look at the Package and Deployment Wizard
> - it's basic, to be sure, but it's served me well in the past and /will/
> locate the need for your OCX, /include/ it in the Package and install
> and register it as your end-user installs it.
>
>> Does all that ocx magic just get wrapped up in the exe and magically
>> work?
>
> Nope.
>
>> So registering a component is just a development phase requirement?
>
> Nope.
>
> COM Components /have/ to be registered before you can use them,
> because you access them either by GUID (Early Bound) or ProgID
> (Late Bound), both of which require mapping, via the Registry, into
> the physical location of the DLL.
>
> HTH,
>    Phill  W.
>
>

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
news:ed3ihizzFHA.1168@TK2MSFTNGP15.phx.gbl...
> "MP" <nospam@Thanks.com> wrote in message
> news:0e43f.74$1A1.64@tornado.rdc-kc.rr.com...
> >
> > or does dw just not list custom ocx's?
> >
> > Thanks
> > Mark
>
> If you want a tool that will show that OCX as a dependency, check this one
> out.
>
> Process Viewer  for Windows (freeware)
> http://www.xmlsp.com/pview/prcview.htm
>
> Just start the viewer, fire up your app, find it in the viewers list,
> right-click, select Modules. Everything your app loads will be there. You
> can export the list to CSV by hitting F2

:-)