-
Notifications
You must be signed in to change notification settings - Fork 1
Installation & Settings
The easiest way how to test Components Manager is just to take the latest exe from our release page. If you are curious, the installer is made by Inno Setup and you can find the installation script in the source code.
If your permission policy is so strict that you can't download any executable file, try to download the zip source code. Unzip it, find the Installers folder and then Output and try to run it from there.
You can always clone the project to your desktop or fork it. However in that case you need to set up the project yourself.
If you don't have the full office suite, you may need to download and install the Microsoft Office Primary Interop Assemblies(PIAs). Building the project shouldn't be any problem (you may have to change the COM Microsoft.Office.Core library (MSO.dll))
Then you will have to set up these in registry Components Manager is a COM Add-In, so it needs to be registered with the VBA Editor.
For 32-bit Office, you need to create this registry key:
HKCU/Software/Microsoft/VBA/VBE/6.0/Addins/VbeComponents.Connect
For 64-bit Office, you need to create the same key, albeit under the Addins64 key instead:
HKCU/Software/Microsoft/VBA/VBE/6.0/Addins64/VbeComponents.Connect
Here are the values to create for that key:
Description (string value): VBE Components Manager VBE Add-in
FriendlyName (string value): VBE Components Manager
CommandLineSafe (DWORD): 0
LoadBehavior (DWORD): 3
- Windows 7 or higher
- NetFramework 4.0
- Microsoft Office 2007 or higher