Visual Studio 2005: Issues When Using Microsoft Visual Studio 2005

  • Article

1   Visual Studio Tools for Office does not support multipart XML schemas 

Visual Studio Tools for Office only supports XmlMaps that are based on a single primary schema, even though Microsoft Office Excel supports XmlMaps that can be composed of a primary schema and optional supporting schema.

To resolve this issue

There is no known resolution.

2   WordDynamicControls sample does not load controls when reopened 

When using the WordDynamicControls sample, adding controls and then closing and reopening the document will sometimes result in the added controls not being saved.

To resolve this issue

There is no known resolution.

3   Both VBA and XLM (Excel 4.0 Macro) code runs when a workbook opens in the designer  

If you have Visual Basic for Applications (VBA) or Excel 4.0 Macro (XLM) code in your workbook event handlers, the code will be executed while the workbook is open in the designer.

To resolve this issue

To ensure that no VBA or XLM code runs while you customize your workbook using Visual Studio Tools for Office, you should remove any VBA or XLM code associated with your workbook before creating a project based on your workbook.

4   Installing Visual Studio Team System on a computer with only Microsoft Office XP installed causes security dialogs to be displayed when Word or Excel is started 

When you start Word or Excel after installing Visual Studio Team System on a computer with only Office XP installed, the following Office security dialog will be displayed:
VSTOWordAdaptor.dll [or VSTOExcelAdaptor.dll]
contains macros by
Microsoft Corporation
Macros may contain viruses. It is always safe to disable macros, but if the macros are legitimate, you might lose some functionality.
The security level is set to High. Therefore, you cannot enable macros from sources that you do not trust.
[] Always trust macros from this source.
[Disable Macros] [Enable Macros] [More Info]
This warning is shown because the Microsoft signature used to sign VSTOWordAdaptor.dll and VSTOExcelAdaptor.dll is not on the list of trusted signatures in Office XP. The Microsoft signature is on the list of trusted signatures in Office 2003.

To resolve this issue

Trust macros from Microsoft Corporation. If you plan to use Visual Studio 2005 Tools for Office you must install a supported version of Office 2003. Installing Office 2003 will add this Microsoft signature to the list of trusted signatures.

5   Removing a table from a dataset when there are bindings to it can cause components from the component tray to be removed when you debug the application 

This issue occurs when you remove a data-bound host control, such as a list object, from the design surface and then remove the table it was bound to from the data source using either the edit feature or the Data Source Configuration Wizard. If you then add a new host control and debug the application, an exception might be generated. When you stop debugging, the design surface is unloaded and data components are removed from the component tray.

To resolve this issue

If you remove a host control from the design surface and then remove the table it was bound to from the data source, you must manually remove the table’s binding source before building the application.

6   Windows Forms control extender properties do not appear for English Excel if the Windows user locale is set to a language other than English 

This issue affects the English version of Excel if the Windows user locale is changed to a language other than English. Certain properties, such as height and width, are not available for Windows Forms controls hosted on the Excel design surface.

To resolve this issue

Install an Office Multilingual User Interface (MUI) pack onto the system. It is not necessary to change the Excel user interface language.

7   Word does not load Visual Studio Tools for Office customizations when the document is opened through HTTP and "Browse in same window" is not selected in Windows Explorer 

The "Browse in same window" property is used by Internet Explorer to determine whether the document is hosted inside the browser or in a separate window. If the document is hosted in a separate window, the customizations do not load and run.

To resolve this issue

Select "Browse in same window" in Windows Explorer.
To locate the "Browse in same window" property:
1) Open Windows Explorer.
2) Click the Tools menu.
3) Click Folder Options.
4) Click the File Types tab.
5) Select DOC in the list of registered file types.
6) Click Advanced.

When you check a Visual Studio Tools for Office document out of source code control, not all of the required files are automatically checked out. This is because generated code is stored in files that are separate from the user interface (UI) control and data component properties of the document.
Changes that were indirectly made to the dependent files will be lost when the document is checked in, because the dependent files were never checked out and so could not be updated.
If only the document is checked out and there is a newer version of the related files on the server, you will not see the latest properties. The properties in the related files on the server will be overwritten if the related files are checked in with the document.

To resolve this issue

Before modifying a checked-in document, make sure to check out all of the related files. When checking in the document, remember to check in all the related files. These files are visible in Solution Explorer, indented beneath the document, when "Show All Files" is selected.

9   Word templates open in Normal view, not Print Layout view, so non-inline controls are not displayed 

Objects in Word that are not inline with text are visible only in Print Layout view. By default UI controls added to a Visual Studio Tools for Office document are inline with text. The layout type can be changed by right-clicking the control, clicking "Format Control..." and then clicking "Layout".
By default, Visual Studio Tools for Office opens Word Templates in Normal view so non-inline controls do not appear.

To resolve this issue

Switch from Normal view to Print Layout view to display the controls.

10   Deleting a control from an inactive Excel sheet at design time might leave auto-generated code behind 

Each worksheet has its own design surface that is loaded on demand. When changes are made to the worksheet, for example, controls are added, deleted, or changed, the design surface detects those changes and updates the generated code.
If, at design time, controls are deleted from an inactive sheet, the generated code can only be partially updated because the design surface has not been instantiated. There are at least two ways this could happen. First, the "Manage Named Ranges" dialog is used to a delete a NamedRange control from an inactive sheet. Second, the Excel document is opened outside Visual Studio, controls are then removed, and then the document is re-opened inside Visual Studio.

To resolve this issue

Activate the worksheet before using the "Manage Named Ranges" dialog to delete a NamedRange control.
To repair build errors, make each affected sheet dirty by editing a property, adding a control to the surface, or deleting a control from the surface. Then rebuild the project.

11   Visual Studio Tools for Office does not natively support 64-bit applications 

By default Visual Studio Tools for Office and other project types generate to "Any CPU" type. However, Visual Studio Tools for Office solutions only work in a 32-bit environment.

To resolve this issue

To run Visual Studio Tools for Office solutions on a 64-bit computer you must change the platform target in the project properties from "Any CPU" to x86, even if you will deploy the application on a 64-bit Windows operating system. You must also make this change to other types of applications, for example console or Windows Forms applications, that use the ServerDocument class.

12   Visual Studio Team System unit testing is not supported in Visual Studio Tools for Office projects 

The unit testing feature, found in the Visual Studio Team System products, is not supported in Visual Studio Tools for Office.

To resolve this issue

There is no known resolution.

Source: Visual Studio 2005: Issues When Using Microsoft Visual Studio 2005