Allows projects to group outputs according to usage.
Assembly: Microsoft.VisualStudio.Shell.Interop.8.0 (in Microsoft.VisualStudio.Shell.Interop.8.0.dll)
Thetype exposes the following members.
|get_CanonicalName||Returns the canonical name of the output group.|
|get_DeployDependencies||Provides access to one or more deployment dependencies.|
|get_Description||Returns the description of an output group.|
|get_DisplayName||Returns the display name of the output group.|
|get_KeyOutput||Returns the canonical name of the key output group.|
|get_Outputs||Returns an array of pointers to IVsOutput2 interfaces providing access to a configuration's output items.|
|get_ProjectCfg||Returns a pointer to the configuration's IVsProjectCfg2 interface.|
|get_Property||Gets the value of a property.|
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.
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.
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.Notes to Implementers
Implemented by project configurations that organize their output items into groups by usage.