Assembly: Microsoft.VisualStudio.Shell.Interop (in microsoft.visualstudio.shell.interop.dll)
[GuidAttribute("910035B1-D8BE-403A-975E-E4FB68CE40A1")] [InterfaceTypeAttribute(1)] public interface IVsComponentUser
/** @attribute GuidAttribute("910035B1-D8BE-403A-975E-E4FB68CE40A1") */ /** @attribute InterfaceTypeAttribute(1) */ public interface IVsComponentUser
IVsComponentUser is used in conjunction with. A package that wants to use the component selector dialog would implement IVsComponentUser and pass it to the service.
The environment provides the default implementation that is used by the standard Add Reference dialog box.
You implement IVsComponentUser on your hierarchy node, then call IVsComponentSelectorDlg with an appropriate filter from theenumeration, pass in your node's IVsComponentUser interface, a GUID_NULL for the show-only page (or GUID_COMPlusPage if that's the one you want on top), a null reference (Nothing in Visual Basic) if you want to enumerate on the local machine, an array of values, your file filter, and a BSTR to set the initial directory and store it on return.
The following are the steps to using the IVsComponentUser interface.
The use selects AddReference which calls the Hierarchy's IOleCommandTarget for AddReference.
The command implementation does a QueryService for SVsComponentSelectorDlg to find IVsComponentSelectorDlg and then calls IVsComponentSelectorDlg with its implementation of IVsComponentUser.
The user selects references to add and clicks the Add button on the dialog.
The dialog calls back on.
The hierarchy's implementation of AddComponent visually adds the reference and physically adds it to the project.
Only projects that support references need to implement this interface.Notes to Implementers Implemented by any VSPackage that wants to use the Component Selector Dialog, such as a Project System that will allow the user to add references to .Net assemblies.