Security for Smart Document DLLs, Add-ins, and Macros [Office 2003 SDK Documentation]
After processing the XML expansion pack manifest file, Microsoft Office 2003 then checks the smart document code files included in the XML expansion pack. These files can include the smart document dynamic-link library (DLL) that contains the smart document intelligence as well as DLL files for add-ins. All of these files require an additional security check.
Note If you have macros that are located inside the smart document itself, the security check for macros happens before the security check for the XML expansion pack.
To do this, Office 2003 reads the XML expansion pack manifest file and locates any files that are part of the smart document. Then each one of these files is subjected to a general Office 2003 security check. This is the same security check that Office 2003 performs when it loads an add-in or a user opens a document that contains macros. For more information on how Office 2003 handles security for add-ins and macros, see General Office Security.
Working with managed smart documents
The previous security guidelines relate primarily to smart documents that are developed using COM languages. However, you can create smart documents using Microsoft .Net languages also. Add-ins that you write in managed code have additional security issues that you will need to address. The following topics are designed to help you understand how security functions for smart document DLLs, add-ins, and macros that you write in managed code.