Microsoft KB Archive/929664

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:35, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Some menu items in Visual Studio 2005 are missing when you open or create a project in Visual Studio 2005 after you install SQL Server 2005 Business Intelligence Development Studio

Article ID: 929664

Article Last Modified on 1/3/2007



APPLIES TO

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition



Bug #: 406692 (SQLBUDT)


SYMPTOMS

Consider the following scenario. You have a computer that is running Microsoft Visual Studio 2005 and Microsoft SQL Server 2005 Business Intelligence Development Studio. Additionally, you never start Visual Studio 2005 before you install SQL Server Business Intelligence Development Studio. You open or create a project in Visual Studio 2005. In this scenario, some menu items in Visual Studio 2005 are missing.

For example, the Attach to Process and Macros commands do not appear on the Tools menu. Additionally, the Step Into command does not appear on the Debug menu.

CAUSE

This problem occurs because Visual Studio 2005 uses the collection of settings for SQL Server 2005 Business Intelligence Development Studio by default.

WORKAROUND

To work around this problem, follow these steps:

  1. In Visual Studio 2005, click Import and Export Settings on the Tools menu. The Import and Export Settings Wizard opens.
  2. On the Welcome to the Import and Export Settings Wizard page, click Import selected environment settings, and then click Next.
  3. Follow the steps in the wizard to the Choose a Collection of Settings to Import page.
  4. On the Choose a Collection of Settings to Import page, select a collection of settings that you want to import, and then follow the steps in the wizard to the end.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kbexpertiseadvanced kbtshoot kbprb KB929664