Office solutions created using Microsoft Visual Studio Tools for the Microsoft Office System contain Microsoft Office Word 2003 and Microsoft Office Excel 2003 projects. Word and Excel projects, at their most essential, are composed of two parts: a Microsoft Office 2003 document and an assembly. An Office document can be a Word document (.doc), an Excel workbook (.xls), or a Word template (.dot). The assembly is a .dll file generated from a Visual Basic (.vb) or C# (.cs) file. The assembly contains managed code that adds functionality to the document.
In This Section
- How to: Create Word and Excel Projects
- Describes how to use the Microsoft Office Project Wizard to create a Word or Excel project using a new or existing document or workbook.
- Assemblies in Office Projects
- Explains the role of managed-code assemblies in Office projects. Also, discusses the issue of keeping the assembly with the Office document versus keeping it on a server.
- How to: Link an Assembly to a Word or Excel File
- Discusses the use of the Assembly Link Location property in determining which assembly is associated with an Office document.
- How to: Add a Referenced Assembly to a Project
- Describes the additional steps you must perform if you add a reference to another assembly to your project.
- How to: Bypass the Assembly When Opening an Office Solution
- Explains how you can open a document or workbook that contains managed code extensions without running the assembly code.
- How to: Add Template Behavior to an Excel Workbook
- Describes how to add functionality to an Excel workbook that allows users to create a local copy of your application as if it were a template.
- Document vs. Template Files
- Discusses the different ways to make your Word document available to your users and briefly describes the advantages of each.
- How to: Handle Errors in Word and Excel Projects
- Explains how the interaction of managed and unmanaged code affects error handling in Word and Excel projects.
- Debugging in Word and Excel Projects
- Presents issues involved in debugging Word and Excel projects that you create using Visual Studio Tools for the Microsoft Office System.
- Threading Support in Office
- Explains why background threads cannot call into the Office object model.
- How to: Build Office Solutions That Use Managed Code Extensions
- Describes how to build your Office solution in Visual Studio .NET and discusses how the assembly location is updated after building.
- Collaborative Development of Office Solutions
- Discusses the extra steps required to enable collaborating developers to open a solution that uses managed code extensions and test the assembly.
- Globalization and Localization of Office Solutions
- Discusses issues involved with localizing Office solutions, including static text, which must be handled separately from the assembly and other managed resources.
- Microsoft Office Project Wizard
- Provides links to reference information on the Microsoft Office Project Wizard, which can be used to create a Word Document project, a Word Template project, or an Excel Workbook project.
- Deploying Office Solutions That Use Managed Code Extensions
- Provides links to information on deploying your solutions, including security concerns, as well as issues to consider when choosing a deployment method.
- Common Tasks in Office Programming
- Lists frequently asked questions about programming with Visual Studio Tools for the Microsoft Office System and provides links to topics that can help solve common problems.
- Programming with Office
- Provides links to information on creating business applications that collect, analyze, manipulate, or present information by taking advantage of the robust functionality of Microsoft Office 2003.