title | ms.custom | ms.date | ms.reviewer | ms.suite | ms.technology | ms.tgt_pltfrm | ms.topic | helpviewer_keywords | ms.assetid | caps.latest.revision | ms.author | manager | translation.priority.mt | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
How to: Add a Dependency to a VSIX Package | Microsoft Docs |
11/04/2016 |
|
article |
|
8f20177b-dab9-43a3-b959-81a591b451d6 |
12 |
gregvanl |
ghogen |
|
You can set up a VSIX package deployment that installs any dependencies that are not already present on the target computer. To accomplish this, include the VSIX dependencies to the source.extension.vsixmanifest file.
-
Open the source.extension.vsixmanifest file in the Design view. Go to the Dependencies tab and click New.
-
To add an installed extension: in the Add New Dependency dialog box, select Installed extension and then, for the Name, select an extension on the list.
-
To add another VSIX that is not installed: : in the Add New Dependency dialog box, select File on file system and then use the Browse button to select the VSIX.
VSIX Extension Schema 1.0 Reference
Anatomy of a VSIX Package
Preparing Extensions for Windows Installer Deployment