I have a VBA Macro on outlook that allows me to forward an email as an attachment to different email addresses.I have customised my outlook ribbon and created a button that is linked to this macro. How would i go by packaging this item (Macro and Ribbon Button) so i can give it to other users to install on their machines?

Thanks,

I think you could do it programatically. I have a process for sharing my Excel macros/ribbon, and you could try modifying it for Outlook. I'd be curious as to whether it works the same, since I'd like to eventually share my outlook macros as well. All the user has to do is run a batch file. There are a couple of components:

1. Create a folder in a shared directory, where you can store your personal macros and ribbon.




2. Copy over your macros from your local folder. For Excel, I copied over my personal excel file where I store my macros, out of C:UsersusernameAppDataRoamingMicrosoftExcelXLSTART. For Outlook, I assume you'd use the VbaProject.OPM file in C:UsersusernameAppDataRoamingMicrosoftOutlook.




3. Copy over your UI file (ribbon) from your local folder: C:UsersusernameAppDataLocalMicrosoftOffice. The Excel ribbon is called Excel.officeUI, and I assume the Outlook ribbon is the file called olkexplorer.officeUI.



4. 
   

   Create your batch file, which will Copy the macros and UI out of the shared directory and on to the user's local drive. It will then call a VBS file which will slightly modify the UI file, replacing occurrences of your username with the user's username. I'm new to batch files and not sure how to insert comments into the code, but you should modify the first path (use the above path where the Outlook OPM file is stored), as well as the name of the macro file and the UI file (VbaProject.OPM and olkexplorer.officeUI).

   
   
   

    Echo off
    cls
    Echo Please ensure that Excel(Outlook) is closed before continuing.
    pause 
    cls
   
    cd YourSharedDirectory
    copy PERSONAL.XLSB c:users%USERNAME%AppDataRoamingMicrosoftExcelXLSTART*.* /y
    cls
   
    cd YourSharedDirectory
    copy Excel.officeUI C:Users%USERNAME%AppDataLocalMicrosoftOffice*.* /y
    cls
   
    @echo off
    wscript "findReplaceUserNameinUI.vbs"
   

   
   


5. 
   

   Create a VBS file (which you run at the end of the batch file) to find YOUR username in the UI file and replace it with the username of the person downloading the macros, since it won't work on their computer otherwise.

   
   
   

   Const ForReading = 1
   Const ForWriting = 2
   
   'get username
   username= CreateObject("WScript.Network").UserName
   
   'change this to the local location for outlook UI
   uiPath = "C:Users" & username & "AppDataLocalMicrosoftOfficeExcel.officeUI"
   
   'open the UI file in notepad, find & replace with new username
   Set objFSO = CreateObject("Scripting.FileSystemObject")
   Set objFile = objFSO.OpenTextFile(uiPath, ForReading)
   strText = objFile.ReadAll
   objFile.Close
   strNewText = Replace(strText, "your user name", username)
   Set objFile = objFSO.OpenTextFile(uiPath, ForWriting)
   objFile.WriteLine strNewText 
   objFile.close
   
   msgbox "Completed!"
   

   
   

Outlook macro aren't made to be disitributed such as in Excel. You should build an add-in in .NET Framework using Office tools.

Here's an introduction : https://docs.microsoft.com/en-us/outlook/add-ins/quick-start?tabs=visual-studio

If you still want to export your macro, there are some workaround :

Solution 1

You can export modules as .bas, .cls, frx, and .frm files.Other users will have to reverse the process by importing them.

With this method no user will lose any code.

BUT

When importing the ThisOutlookSession module, it will be renamed ThisOutlookSession1. You'll have to copy the code from here and paste it in ThisOutlookSession or it won't run.

Solution 2

If the users don't have any macro project in their Outlook, you can copy (assuming there is only this macro on your Outlook) the VBAProject.OTM that you can find in %AppData%MicrosoftOutlook and overwrite the user's one with it.

The last method is the one I used when I had to share a macro. But if I knew it would be such a ****** I would have use VB.NET immediately. There are other solutions but I never experimented them.

VBA macros are not designed for distributing solutions on other/multiple machines. Moreover, VBA macros doesn't allow to customize the Fluent UI (aka Ribbon UI) programmatically. You need to develop a COM based add-in for these reasons. That is for they were invented! See Walkthrough: Create your first VSTO Add-in for Outlook to get started quickly.

You can read more about the Fluent UI (aka Ribbon UI) in the following series of articles:

• Customizing the 2007 Office Fluent Ribbon for Developers (Part 1 of 3)


• Customizing the 2007 Office Fluent Ribbon for Developers (Part 2 of 3)


• Customizing the 2007 Office Fluent Ribbon for Developers (Part 3 of 3)

VSTO provides two main ways for creating a custom ribbon UI:

• Walkthrough: Create a custom tab by using the Ribbon Designer


• Walkthrough: Create a custom tab by using Ribbon XML

In case you still want share your VBA macro see To distribute Microsoft Outlook VBA code to other users for possible solutions.