Applies to
The information in this topic applies only to the specified Visual Studio Tools for Office projects and versions of Microsoft Office.
Project type
Document-level projects
Application-level projects
Microsoft Office version
Microsoft Office 2003
For more information, see Features Available by Application and Project Type.
Visual Studio Tools for Office solutions incorporate the security features available with the Microsoft .NET Framework. In addition, it sets policy at the application domain level that prevents code from running until it is explicitly granted permission.
Discusses security from the perspective of the developer, end user, and administrator.
Describes some security best practices for Visual Studio Tools for Office solutions, including adding conditions to security policy, checking the current policy, and setting default policy.
Describes how to change security settings while you develop assemblies on your own computer.
Describes the methods you can use to remove trust from folders and assemblies.
Discusses how you can use the Office Document Membership Condition to grant permissions only to the documents and workbooks that are in a specific location.
Demonstrates how to replace the default permissions that were granted during project development with permissions based on strong name.
Provides links to other topics in Visual Studio that discuss security risks.
Provides links to information about what you need to create projects using Visual Studio Tools for Office.
Provides information about the considerations involved in choosing a local or network deployment model.
Provides links to information about how Visual Studio Tools for Office solutions work.