|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
Assembly: Microsoft.VisualStudio.Shell.Interop (in microsoft.visualstudio.shell.interop.dll)
[GuidAttribute("66899421-F497-4503-8C9D-ADAE290F2F27")] [InterfaceTypeAttribute(1)] public interface IVsComponentSelectorDlg
/** @attribute GuidAttribute("66899421-F497-4503-8C9D-ADAE290F2F27") */ /** @attribute InterfaceTypeAttribute(1) */ public interface IVsComponentSelectorDlg
is used in conjunction with IVsComponentSelectorDlg. A VSPackage 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 steps are for using the IVsComponentUser interface.
The user 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 addcomponent.
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 The environment implements this interface.