VBE Add-Ins are Missing In Action 1

[VB400]

When I login as the administrator on my NT Workstation machine, I see a ton of Add-Ins in the Add-In manager. When I log in as myself, I get just a couple.

Any thought?
[sig]<p> Tarek<br><a href= > </a><br>The more I learn, the more I need to learn![/sig]

 

[NFI]

Hiya,

Add-Ins are specific to the user who installed VB in the first place, the DLL's and OCX's that make up the Add-Ins are only registered in the registry for that user. This is, in reality, a bug in VB in my opinion (and in the opinions of our admin chaps) and the only way around it is to register the DLL's and OCX's for each user, using Regsvr32.

What we do where I work is have a script which registers all the most common Add-Ins, which you can then run if you ever lose your Add-Ins if, for instance, your Domain Controller goes down and you have to create a new profile.

Here's the script we use, obviously you'll probably want to change the various drive letters and directories and you possibly won't want all the libraries involved, but if you save this as a .cmd file and run it, it'll register all the standard Add-Ins that come with VB Enterprise Edition. If you try to register a component that doesn't exist, the script will just carry on anyway without erroring.

Hope this helps,

Cheerio,

Paul

@REM
@REM This will register all the vb addins to return them to usability@REM
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\PDADDIN.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\CTRLWIZ.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\AXDOCWIZ.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\AITOOL.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\\Common\Tools\Winapi\APILOAD.EXE&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\APPWIZ.OCX&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\CLSSBLD.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\DATAFORM.OCX&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\MSDATOBJ.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\PROPPGWZ.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\RESEDIT.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\TEMPMGR.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\WIZMAN.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\VB98\Tsql\VBSDIADD.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\Common\Tools\VCM\VCMMGR.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\Common\Tools\VS-Ent98\vmodeler\RVBADDIN.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\Common\Tools\VS-Ent98\vmodeler\RVBADDINMENUS.DLL&quot; /s
regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\Common\Tools\VS-Ent98\vmodeler\RVBADDINMENUS.DLL&quot; /s
[sig][/sig]

 

[VB400]

Paul,

How do you actually run this script? [sig]<p> Tarek<br><a href= > </a><br>The more I learn, the more I need to learn![/sig]

 

[NFI]

Hiya,

cut and paste all of the text after and including the @REM into a text editor (notepad for instance) and save the file as AddInSetup.cmd. You can pretty much call it anything you like, but the .cmd extension is important, as this is what denotes it as being a command script, which is very much like a batch file. Then, from the command prompt, type the name of the script you just saved (AddInSetup if you called it that) and press return. The script will then run and register all the relevent DLL's and OCX's. Alternatively, from explorer, you can double click on the script and run it that way - it'll open its own DOS window and close it upon completion.

Cheerio,

Paul [sig][/sig]

 

[VB400]

Thanks a bunch Paul, this really helps!

One of the lines points to an EXE file:

regsvr32 &quot;d:\Program Files\Microsoft Visual Studio\\Common\Tools\Winapi\APILOAD.EXE&quot; /s

Can you actually register an EXE? The API Viewer still doesn't show up in the Add-In Manager!
[sig]<p> Tarek<br><a href= > </a><br>The more I learn, the more I need to learn![/sig]

 

[NFI]

You can register some .exe applications, as it is possible to write an executable which also behaves as an ActiveX Server, which means they can be treated the same as registerable .dll libraries. They can also be used as stand alone executables, the overhead is that communication between an ActiveX exe instantiated as an object and the instantiating program is far slower than that between an ActiveX dll and the instantiating program. The reason for this is that a dll and its calling program share the same address space, so the data transfer between them is very efficient, even allowing for the overheads COM (the underlying standard that handles object interactivety) adds for ActiveX dll's. An ActiveX exe, however, even when instantiated as an object, is a seperate program altogether, so has its own process / address space in memory. COM must set up a communication system called marshelling to transfer data across the process boundary between the ActiveX object and the calling program, for which the overhead of doing so is relatively high.

Fascinating, but not particularly vital to know...

The API viewer should be registered by the script I gave you, you might want to check that the relative component is present in your system. The one you're looking for is, in fact, the .exe you pointed out. It should appear in the Add In Manager list as VB6 API Viewer.


Cheerio,

Paul [sig][/sig]