Hit F5 or click the Start button with the green arrow on the main Visual Studio toolbar to build and launch the solution. Visual Studio will automatically build the add-in, register it in Excel and launch this app so that you can see our Excel VSTO example in action:. Most likely, the WinForms form will be somewhere in the background and you will need to click the corresponding taskbar button to bring it to the front.
There are solutions allowing you to keep the form on top of the main Excel window like this , but they are beyond the scope of basic introduction to building of VSTO add-ins described in this article. When we compile and launch our example of Excel VSTO add-in with the modified Startup event handler, we should see this:. Ok, now we know how to add a WinForms control to a form and can do this for the iGrid grid control. NET X v Click the OK button.
This action must add the reference to the iGrid control to our Excel add-in project:. Pay attention to the fact that a reference to the System. This allowed us to use the standard button control included into this library in our Excel add-in example.
However, we must add a reference to any third-party control like iGrid manually before we can use it in the add-in. To create a document-level customization project for Excel, use the Excel workbook or Excel template project templates in the New Project dialog box of Visual Studio. For more information about how document-level customizations work, see Architecture of document-level customizations. When you create a document-level project for Excel, Visual Studio generates several classes that are the foundation of your solution: ThisWorkbook , Sheet1 , Sheet2 , and Sheet3.
These classes represent the workbook and worksheets that are associated with your solution, and they provide a starting point for writing your code. For more information about these generated classes and other features you can use in a document-level project, see Program document-level customizations. The assembly typically extends Excel by customizing the UI and by automating Excel. Unlike a document-level customization, which is associated with a specific workbook, functionality that you implement in a VSTO Add-in is not restricted to any single workbook.
This class provides a starting point for writing your code, and it also exposes the object model of Excel to your VSTO Add-in.
There are several different ways to customize the user interface of Excel. Some options are available to all project types, and other options are available only to VSTO Add-ins or document-level customizations. The following table lists customization options that are available to both document-level customizations and VSTO Add-ins. The following table lists customization options that are available only to document-level customizations. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. For more information, see Limitations of global templates and Excel Add-ins. Program document-level customizations. Walkthrough: Create your first document-level customization for Word. Walkthrough: Create your first document-level customization for Excel. When you create a project that is based on one of these project templates, the code in your solution runs when the associated application is open.
Unlike document-level projects, your code is not associated with a single document. When you design a solution around a Word document or Excel workbook, you must decide the best way to make that document available to your users. 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. In some situations, you might want to give a copy of a document to each user. In this case, create your solution by using an Excel or Word document project. In other situations you might want to make a template available on a server, so that each user can open the template and save a local copy as a document. In this case, create your solution by using an Excel or Word template project.
If a Microsoft Office Word template has managed code extensions, the project assembly is not called if the template is attached as a global template or loaded from the startup directory of Word.
In addition, the document does not recognize the format of a template that is part of an Office solution. It is possible to save a workbook as an. In some cases, your code will run in the target workbook after the VSTO Add-in is applied, but such use of the Office solution is not supported.
0コメント