What's New in the Visual Studio 2015 SDK
This article applies to Visual Studio 2015. If you're looking for Visual Studio 2017 documentation, use the version selector at the top left. We recommend upgrading to Visual Studio 2017. Download it here.
The Visual Studio SDK has the following new and updated features for Visual Studio 2015, Visual Studio 2015 updated, and Visual Studio 2017.
Visual Studio 2017
Starting in Visual Studio 2017, scanning for custom project and item templates will no longer be performed. Instead, the extension must provide template manifest files that describe the install location of these templates. You can use Visual Studio 2017 to update your VSIX extensions. If you deploy your extension using an MSI, you must generate the template manifest files by hand. For more information, see Upgrading Custom Project and Item Templates for Visual Studio 2017. The template manifest schema is documented in Visual Studio Template Manifest Schema Reference.
VS 2015 SDK Update 1
Update 1 includes tools to help your extension work well with color themes and the Visual Studio image service.
These topics are under the VSSDK Utilities section:
The Color Theming Tools help you create and edit custom colors for Visual Studio.
The Image Service Tools let you work with Visual Studio image manifest files.
New Way to Add the Visual Studio SDK to Visual Studio
Starting in Visual Studio 2015, you don't need to download the Visual Studio SDK separately. Instead, you can install it as part of the normal installation process, or you can choose to install it later on. When you open or create a VSIX solution, Visual Studio will ask you to install the Visual Studio Extensibility Tools. For more information, see Installing the Visual Studio SDK.
New Ways of Creating Extensions
Starting in the Visual Studio 2015 SDK, you have different options for creating extensions, depending on which programming language you’re using.
Visual C# and Visual Basic
For C# and Visual Basic, there is a full range of project item templates that allow you to create VSPackages, menu commands, tool windows, editor classifiers, editor adornments, and editor margin extensions. You can add any or all of these to the standard VSIX project. For more information, see:
The VSPackage Wizard no longer creates extensions in C# or Visual Basic.
For C++, the VSPackage Wizard support menu commands, tool windows, and custom editors. Look for it in the New Project dialog in Visual C++ / Extensibility.
VS SDK Reference Assemblies via NuGet
For increased portability and sharing of extensibility projects, you can use the NuGet versions of the VS SDK reference assemblies. These are available on nuget.org published by VisualStudioExtensibility and can be easily added to your project or solution through the Visual Studio References / Manage NuGet Packages dialog. You can add individual references to specific extensibility assemblies or add all the VS SDK references assemblies at once using the VS SDK Meta package. To learn more about NuGet, see NuGet Overview and Manage NuGet Packages Using the Dialog.
When you use the NuGet versions of the VS SDK reference assemblies, another user doesn’t need to install the VS SDK to open and build your project. The NuGet reference assemblies and VS SDK build tools will automatically be installed on their computer for that project.
The VS SDK item templates use NuGet for their references and build tools so you get the benefits of NuGet by default.
You can continue to use the VS SDK installed reference assemblies with your projects (located under <Visual Studio Install Location>\ VSSDK\VisualStudioIntegration\Common\Assemblies) and existing extensibility projects do not need to be upgraded to use NuGet packages. The project References / Add Reference dialog continues to use the VS SDK installed reference assemblies.
If you’d like to modify your existing projects to use NuGet, see How to: Migrate VSPackages to Visual Studio 2015 which has a section on updating extensibility projects to NuGet packages.
One of the most exciting new ways of writing extension code is provided by the Roslyn project. For more information, see Roslyn.
Light bulbs are a new feature that ships with the VSSDK. They are icons used in the Visual Studio editor that expand to display a set of code refactoring actions or fixes for problems identified by the built-in code analyzers. For more information, see Walkthrough: Displaying Light Bulb Suggestions.
Updated User Experience Guidelines
Designing new extensions or features for Visual Studio? Check out the updated and expanded Visual Studio User Experience Guidelines. You’ll find the color tokens, font sizes, dialog layout specifications, and other guidance you need to seamlessly integrate your new UI with Visual Studio.