Packages

  • Visual Studio 2013 SDK Samples
    The Visual Studio 2013 SDK will help you extend all aspects of the Visual Studio IDE.  These samples will help provide examples on how to extend the following areas of Visual Studio:

    • Adding menus and commands into the Menu system
    • Creating new Tool Windows
    • Extending the built in code editor
    • Creating new project and item templates
    • Creating and distributing custom controls
    • Adding new options in the Tools options dialog
    • Working with existing assests in project systems
    • Extending MSBuild
    • Creating new project systems
    • Managed, native and custom Debugger integration
  • Visual Studio 2010 SDK Samples
    The Visual Studio 2010 SDK will help you extend all aspects of the Visual Studio IDE.  These samples will help provide examples on how to extend the following areas of Visual Studio:

    • Adding menus and commands into the Menu system
    • Creating new Tool Windows
    • Extending the built in code editor
    • Creating new project and item templates
    • Creating and distributing custom controls
    • Adding new options in the Tools options dialog
    • Working with existing assests in project systems
    • Extending MSBuild
    • Creating new project systems
    • Managed, native and custom Debugger integration
    • Building and deploying applications with the Visual Studio 2010 Shell (Integrated or Isolated)
  • All-In-One Visual Studio Extensibility Code Samples
    The All-In-One Visual Studio Extensibility (VSX) code samples demonstrate the typical programming topics about extending Visual Studio.
  • Microsoft/VSSDK-Extensibility-Samples (GitHub)
    Customize Visual Studio using the VSSDK. You can use extensions to customize the appearance and behavior of the Visual Studio.
  • Visual Studio customization with lightweight extensions and Visual Commander
    It shows the most “popular” interfaces to help you get started with Visual Studio customization using code.
  • HOWTO: Package with commands created by code
    While most of the time a package will create its commands using a .vsct file, so that they are also added to commandbars, menus, etc. there may be situations in which a package needs to create a command by code dynamically, even without knowing the command name at compile time.
  • HOWTO: Get the EnvDTE.DTE instance from a package
    Although a package can use Visual Studio services, sometimes it may need to use the automation model (EnvDTE). To get the EnvDTE.DTE instance, you can use the SDTE service.
  • VS 2017: Visual Studio Setup Configuration Samples
    The included samples show how to use the new setup configuration API for discovering instances of Visual Studio 2017.
Email this to someoneTweet about this on TwitterShare on LinkedInShare on FacebookShare on Google+

VS SDK, packages, add-ins, macros and more…