IVsOutputGroup Interface
Allows projects to group outputs according to usage.
Namespace: Microsoft.VisualStudio.Shell.Interop
Assembly: Microsoft.VisualStudio.Shell.Interop (in Microsoft.VisualStudio.Shell.Interop.dll)
Syntax
'Déclaration
<GuidAttribute("FCC03D95-7C2E-4398-AAAE-0F4B56104FC8")> _
<InterfaceTypeAttribute()> _
Public Interface IVsOutputGroup
'Utilisation
Dim instance As IVsOutputGroup
[GuidAttribute("FCC03D95-7C2E-4398-AAAE-0F4B56104FC8")]
[InterfaceTypeAttribute()]
public interface IVsOutputGroup
[GuidAttribute(L"FCC03D95-7C2E-4398-AAAE-0F4B56104FC8")]
[InterfaceTypeAttribute()]
public interface class IVsOutputGroup
public interface IVsOutputGroup
Remarks
Grouping output items allows project configurations to categorize by usage. For example, a DLL file might be grouped with its PDB file. The project must return the same number of groups for each configuration that it supports, even though the number of outputs contained within a group might vary from configuration to configuration. For example, the group "Matt's DLL" might include mattd.dll and mattd.pdb in debug configuration, but only include matt.dll in retail configuration.
Groups may also have a key output that allows packaging shortcuts to point to something meaningful. Any group might be empty in a given configuration, so no assumptions should be made about the size of a group.
If a project has an IVsOutput2 object that it does not want to package or deploy, it is sufficient to not put that output in a group.
Callers can access a configuration's output groups by calling get_OutputGroups or OpenOutputGroup.
See illustrations of the implementation and/or calling of this interface in the samples Basic Project and My C Package.
Notes to Implementers:
Implemented by project configurations that organize their output items into groups by usage.
Notes to Callers:
Called by the environment and deployment projects during deployment operations.
These groups will also have the same identifier information (canonical name, display name, and group information) from one configuration to another within a project. This allows deployment and packaging to continue to operate even if configurations change.