Visual Studio 2010 SDK Beta 2 Supplemental Readme

The Visual Studio 2010 Beta 2 Documentation is available here.

The DSL Tools for Beta 2 is available here.

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

 

ISSUE: Building a project that generates a VSIX file fails when including a large file in the project.

WORK AROUND: This happens when a file greater than 10 MB is added to the project and marked to be included in the VSIX.  To work around the issue, build your solution using MSBuild from the commandline.  This issue will be fixed in the release after Beta 2.

 

ISSUE: Creation of a Custom Editor with uppercase unicode letters in the project name fails.

WORK AROUND: To work around this issue, avoid using only uppercase unicode letter in the project name.

 

ISSUE: Isolated shell projects display unnecessary item templates without an icon. 

WORK AROUND: There is no work around to this issue.  The item templates are benign and do not affect the Isolated Shell.

 

ISSUE: Deleting Project or Item templates through the Manifest Editor does not remove the template from the VSIX output.

WORK AROUND: To work around this issue, manually remove the template zip file in your project when removing the Project or Item template through the manifest editor.

 

ISSUE: The copy build task in the VSSDK.targets file copies the project or item templates to the Local Application Data location instead of the bin/debug folder. 

WORK AROUND: If the desired output location is the bin/debug folder and not the Local Application Data folder, follow these steps:

1. Disable copying to Local Application Folder by updating the project file:

<DeployVSTemplates>false</DeployVSTemplates>

2. To enable copying to bin/debug, add the following to the project file:

<PropertyGroup>

<CreateVsixContainerDependsOn>$(CreateVsixContainerDependsOn);GetMyTemplates</CreateVsixContainerDependsOn>

</PropertyGroup>

<Target Name="GetMyTemplates">

<ItemGroup>

<VSIXSourceItem Include="@(IntermediateZipItem)">

<VSIXSubPath>SharePoint\2010\1033\</VSIXSubPath>

</VSIXSourceItem>

</ItemGroup>

</Target>

 

 

ISSUE: Unable to add a reference to your existing VSIX project through the manifest designer.

WORK AROUND: This issue occurs when a developer tries to add a new assembly to their VSIX project and uses the manifest designer to reference the same project.  To work around this, add the new assembly in a separate project and reference that through the manifest editor.  This issue will be fixed in the first release after Beta 2.

ISSUE: Unable to use Createpkgdef to generate a pkgdef file from registration attributes.

WORK AROUND: When using registration attributes in your code to auto generate a pkgdef file, you will need to add the registration attribute code found in the MPF Sources in your VS SDK install.  The source can be found in the VS SDK installation folder under VisualStudioIntegration\Common\Source\CSharp\RegistrationAttributes.

ISSUE: Unable to edit a xaml file.

WORK AROUND: The reference assemblies installed by the Visual Studio SDK are a slimmed down version of the full reference assemblies.  When editing a xaml file, this mismatch may cause the editor to not allow users to edit their files xaml files inside of VS.

To workaround this issue, copy the reference assemblies that your project requires into the Global Assembly Cache.

 

ISSUE: UI DLLs do not get copied to the correct folder for C++ projects.

WORK AROUND: When building a C++ project (including the Visual Studio Isolated Shell), the UI DLL does not get copied to the locale specific folder (such as \1033).  This causes the menu items of the packages to now appear in the Visual Studio IDE. 

To workaround this issue, manually copy and deploy your UI.DLL into the locale specific folder.

 

ISSUE: Visual Studio 10 Beta 2 may fail to load some MEF assemblies that are installed as part of a VSIX.  This issue affects MEF assemblies defining new types that are used in MEF metadata.  For example, an extension defining its custom text tag derived from the Visual Studio 2010 Editor's TextMarkerTag type.

WORK AROUND: Create a .pkgdef file and place it in the same folder where the MEF assembly is located.  Add the following two lines to the pkgdef file and replace the {GUID} part with any unique GUID.  Then restart Visual Studio.

[$RootKey$\BindingPaths\{guid}]

"$PackageFolder$"=""