| Contents | Index |
The table Application Deployment Roles, Goals, and Tasks describes the different roles, or jobs, that MATLAB Builder EX users typically perform. It also describes tasks they would most likely perform when running the examples in this documentation.
You may occupy one or more of the following roles.
Application Deployment Roles, Goals, and Tasks
| Role | Goals | Task To Achieve Goal |
|---|---|---|
|
|
| See Creating a Microsoft Excel Add-In and COM Component. |
|
|
| See Integrating Your Add-In and COM Component with Microsoft Excel |
|
|
| See Microsoft Excel Add-in Integration |
To use the MATLAB Builder EX product, specific requirements exist for each user role.
| Role | Requirements |
|---|---|
|
|
|
|
| Moderate to expert user of Microsoft Excel |
|
| Expert at providing customized Microsoft Excel spreadsheet solutions |
Install the following products to run the example described in this chapter:
MATLAB
MATLAB Compiler
MATLAB Builder EX
For more information about product installation and requirements, see MATLAB Compiler Installation and Configuration.
The first time you use MATLAB Compiler, after starting MATLAB, run the following command:
mbuild -setup
For more information about mbuild -setup, see Installation and Configuration.
If you need information about writing MATLAB files, see the MATLAB documentation.
Be sure to choose a supported compiler. See Supported Compilers.
If you will be creating macros and generating add-ins with MATLAB Builder EX, adjust the security settings accordingly in Microsoft Excel.
Failure to do so may result in add-ins not being generated or warning messages sent to MATLAB Compiler
Depending on what version of Microsoft Office you are using, do one of the following:
For Microsoft Office 2003:
Click
Tools > Macro > Security.
For Security Level, select Medium.
For Microsoft Office 2007:
Click the 2007 Office ribbon button (
).
Click Excel Options > Trust Center > Trust Center Settings > Macro Settings.
In Developer Macro Settings, select Trust access to the VBA project object model.
For Microsoft Office 2010:
Click File > Options > Trust Center > Trust Center Settings > Macro Settings.
In Developer Macro Settings, select Trust access to the VBA project object model.
Before you deploy a component with MATLAB Builder EX, consider if your target machines are 32-bit or 64-bit.
Applications developed on one architecture must be compatible with the architecture on the system where they are deployed.
For example, if you have a 64-bit system, you usually install a 64-bit version of MATLAB (and most other applications), by default. Running functions you have developed with a 64-bit version of MATLAB requires a Function Wizard installed with a 64-bit version of Microsoft Excel.
If you are migrating to the 64-bit version of Microsoft Excel, you must uninstall the 32-bit version of MATLAB Builder EX before installing the 64-bit version of Microsoft Excel.
Before you deploy your code, examine the code for dependencies on functions that may not be compatible with MATLAB Compiler.
For more detailed information about dependency analysis (depfun) and how MATLAB Compiler evaluates MATLAB code prior to compilation, see MATLAB Code Deployment in the MATLAB Compiler User's Guide.
| If you... | See... |
|---|---|
| Want to verify your MATLAB code or function can be deployed successfully | MATLAB Code Deployment |
| Know your function is deployable and want to select a Getting Started workflow | Choosing the Appropriate Workflow |
![]() | Product Overview | Choosing the Appropriate Workflow | ![]() |

Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |