Re: auto-REregistering VB6 components?

"javelin" <google.1.jvmail@xxxxxxxxxxxxxxx> wrote in message
news:1164995877.646063.166330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ken, you're obviously used to doing things the manual way, which
results in a greater level of knowledge (usually ) and control. I hope
to get there some day, but I need a solution to this problem for now.
I'd be curious to know where your components appear under in the
components manager. I thought you were required to put them under some
application package.

They don't appear anywhere as far as that manager's concerned. I used the
Add-In Manager to disable the 'Visual Component Manager' so, as far as VBs
concerned, it doesn't exist.

In all the years I've been posting to these groups, only one person (that I
know of) has ever mentioned using Visual Component Manager.

There's no requirement to put them anywhere... if you're talking about
building a setup package, I use InstallShield Express and test the packages
on Virtual PC (which is free now, if interested).. as far as getting a list
of dependencies goes, InstallShield (even the Express version) will
automatically gather them as you run your app (thru InstallShield's
interface).

VB6 is the only version of VB that had any sort of 'Component Manager', as
far as I know.

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
In Loving Memory - http://www.vbsight.com/Remembrance.htm


.

Relevant Pages

  • SUNWesm
    ... I am looking for the SUNWesm package for managing a fiber switch. ... believe that it used to come with Component Manager, ... that Sun has stopped distributing this package. ...
    (comp.unix.solaris)
  • Re: Error message: Subscript out of range
    ... No other indications of VB not ... Visual Component Manager ... You can unload that add-in by ...
    (microsoft.public.vb.general.discussion)
  • Re: Error message: Subscript out of range
    ... No other indications of VB ... Visual Component Manager ... You can unload that add-in by ...
    (microsoft.public.vb.general.discussion)
Loading