Kick-Start Security and .NET
If you save and close the workbook you just created, you’ll see the warning in Figure 1-17 the next time you open it:

Figure 1-17. Macro security warning in Excel
You’re probably very familiar with this warning, and you also probably know that if you digitally sign the code from within the Visual Basic editor, you can change the warning to look something like Figure 1-18.
That’s a little less frightening, and if you (or your users) select Always trust macros from this publisher, Excel will automatically enable macros that have your digital signature without warning—at least under the default security settings.

Figure 1-18. Signed macro security warning in Excel
With Excel VBA, digital signatures are the only way to grant or deny the permission to run code on the user’s machine. VBA code is distributed as workbooks, templates, or add-ins and the code in each of those files must be signed before it is trusted.
There are some problems with this approach: users may choose to trust a publisher who isn’t trustworthy—trust is an all-or-nothing proposition—and updating macros means sending out new files to all users. Excel 2003 addresses these problems by allowing you to program workbooks using the .NET Framework and code-behind assemblies. The .NET Framework ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access