Partilhar via

How to: Expose code to VBA in a Visual C# project

  • Artigo

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

You can expose code in a Visual C# project to Visual Basic for Applications (VBA) code if you want the two types of code to interact with each other.

The Visual C# process is different from the Visual Basic process. For more information, see How to: Expose code to VBA in a Visual Basic project.

Applies to: The information in this topic applies to document-level projects for Excel and Word. For more information, see Features available by Office application and project type.

Expose code in a Visual C# project

To enable VBA code to call code in a Visual C# project, modify the code so it is visible to COM, and then set the ReferenceAssemblyFromVbaProject property to True in the designer.

For a walkthrough that demonstrates how to call a method in a Visual C# project from VBA, see Walkthrough: Call code from VBA in a Visual C# project.

To expose code in a Visual C# project to VBA

  1. Open or create a document-level project that is based on a Word document, Excel workbook, or Excel template that supports macros, and that already contains VBA code.

    For more information about the document file formats that support macros, see Combine VBA and document-level customizations.

    Note

    This feature cannot be used in Word template projects.

  2. Ensure that VBA code in the document is allowed to run without prompting the user to enable macros. You can trust VBA code to run by adding the location of the Office project to the list of trusted locations in the Trust Center settings for Word or Excel.

  3. Add the member that you want to expose to VBA to a public class in your project, and declare the new member as public.

  4. Apply the following ComVisibleAttribute and ClassInterfaceAttribute attributes to the class that you are exposing to VBA. These attributes make the class visible to COM, but without generating a class interface.

    [System.Runtime.InteropServices.ComVisible(true)]
[System.Runtime.InteropServices.ClassInterface(
    System.Runtime.InteropServices.ClassInterfaceType.None)]

  5. Override the GetAutomationObject method of a host item class in your project to return an instance of the class that you are exposing to VBA:

    • If you are exposing a host item class to VBA, override the GetAutomationObject method that belongs to this class, and return the current instance of the class.

      protected override object GetAutomationObject()
{
    return this;
}

    • If you are exposing a class that is not a host item to VBA, override the GetAutomationObject method of any host item in your project, and return an instance of the non-host item class. For example, the following code assumes that you are exposing a class named DocumentUtilities to VBA.

      protected override object GetAutomationObject()
{
    return new DocumentUtilities();
}

      For more information about host items, see Host items and host controls overview.

  6. Extract an interface from the class that you are exposing to VBA. In the Extract Interface dialog box, select the public members that you want to include in the interface declaration. For more information, see Extract interface refactoring.

  7. Add the public keyword to the interface declaration.

  8. Make the interface visible to COM by adding the following ComVisibleAttribute attribute to the interface.

    [System.Runtime.InteropServices.ComVisible(true)]

  9. Open the document (for Word) or worksheet (for Excel) in the designer in Visual Studio.

  10. In the Properties window, select the ReferenceAssemblyFromVbaProject property, and change the value to True.

    Note

    If the workbook or document does not already contain VBA code or if VBA code in the document is not trusted to run, you will receive an error message when you set the ReferenceAssemblyFromVbaProject property to True. This is because Visual Studio cannot modify the VBA project in the document in this situation.

  11. Click OK in the message that is displayed. This message reminds you that if you add VBA code to the workbook or document when running the project from Visual Studio, the VBA code will be lost the next time that you build the project. This is because the document in the build output folder is overwritten every time that you build the project.

    At this point, Visual Studio configures the project so that the VBA project can call into the assembly. Visual Studio also adds a method named GetManagedClass to the VBA project. You can call this method from anywhere in the VBA project to access the class that you exposed to VBA.

  12. Build the project.

See also