Visual Studio 2010 SDK Beta 1 Readme

  • Article

Visual Studio 2010 SDK Beta 1 Supplemental Readme

The Visual Studio 2010 Beta 1 Documentation is available here.

The DSL Tools for Beta 1 is available here.

This posting contains additional readme and known issues about the Visual Studio 2010 SDK Beta 1 release.  These are in addition to the known issues that were included in the installation of the Visual Studio 2010 SDK Beta 1.

 

ISSUE: Debugging my extension in the experimental instance takes a long time

WORKAROUND: To workaround the issue, disable the Historical Debugger by going to the Tools menu, select Options, and then select Historical Debugger

 

ISSUE: Using a unicode character in the project name of a Visual Studio Extension causes the deployment of the extension to fail.

WORKAROUND: This is a known issue which will be fixed for the next Visual Studio 2010 public release.  The workaround is to not use a unicode character in the project name.

 

ISSUE: The Isolated Shell Project does not work with Editor extension projects.

WORKAROUND: This is a known issue which will be fixed for the next Visual Studio 2010 public release.  The workaround is to build the extensions separately and drop the extension with the extension.vsixmanifest file in the %ShellFolder%\Extensions folder for the Isolated Shell to pick it up on launch.

 

ISSUE: When adding a reference to Microsoft.VisualStudio.Shell.10.0.Interop.dll, I get build errors.

WORKAROUND: This is a known issue which will be fixed for the next Visual Studio 2010 public release.  The workaround is to set the property "Embed Interop Types" of the reference to "false".

 

ISSUE: When migrating a Visual Studio 2008 project to Visual Studio 2010 and adding a reference to Microsoft.VisualStudio.Shell.dll, Microsoft.VisualStudio.Shell.9.0.dll, Microsoft.VisualStudio.Package.LanguageService.dll, or Microsoft.VisualStudio.Package.LanguageService.9.0.dll, I still get build errors.

WORKAROUND: This is a known issue which will be fixed for the next Visual Studio 2010 SDK public release.  The problem occurs because the reference assemblies in the SDK for these binaries inadvertently had their assembly version changed from 2.0 to 10.0.

To workaround this issue, follow these steps:

1) Navigate to your GAC location under <RootDrive>\Windows\Assembly\GAC_MSIL and find Microsoft.VisualStudio.Shell.dll, Microsoft.VisualStudio.Shell.9.0.dll, Microsoft.VisualStudio.Package.LanguageService.dll, and Microsoft.VisualStudio.Package.LanguageService.9.0.dll (assembly version 2.0)

2) Copy the assemblies to %VSSDKInstallDir%\VisualStudioIntegration\Common\Assemblies

3) Inside your project, use the Add References dialog and add a reference to the assemblies you copied over (if necessary)

4) Build your project.

 

ISSUE: When migrating a Visual Studio 2008 package to Visual Studio 2010, the package is not loaded.

 

WORKAROUND: You need to add a extension.vsixmanifest file to your project.  To do so, you can get one from a new Visual Studio 2010 package project and adjust it for your own package.

 

 

ISSUE: After installing an extension, the extension doesn't get loaded.

 

WORKAROUND: Ensure extensions can be loaded from your %LocalAppData% directory.  If you're an administrator on the machine, go to Tools/Options, select Extension Manager and check "Load extensions from my Local Applicaton Data folder"

 

 

ISSUE: The Visual Studio 2010 SDK Beta 1 install fails after clicking the "Next" Button

 

WORKAROUND: There are two potential work arounds.

 

Uninstall the Visual Studio 2008 SDK

 

or

 

1) Extract the SDK package by typing:

      vssdk_full.exe /x

2) Enter a directory to extract the files to

3) Navigate to the directory

4) Launch the .MSI file