IVsOutputGroup2 Interface

Allows projects to group outputs according to usage.

Namespace:  Microsoft.VisualStudio.Shell.Interop
Assembly:  Microsoft.VisualStudio.Shell.Interop.8.0 (in Microsoft.VisualStudio.Shell.Interop.8.0.dll)

[GuidAttribute("06A3B841-FBEA-46CB-81EA-36DB4D005545")]
[InterfaceTypeAttribute()]
public interface IVsOutputGroup2 : IVsOutputGroup

The IVsOutputGroup2 type exposes the following members.

  NameDescription
Public methodget_CanonicalNameReturns the canonical name of the output group.
Public methodget_DeployDependenciesProvides access to one or more deployment dependencies.
Public methodget_DescriptionReturns the description of an output group.
Public methodget_DisplayNameReturns the display name of the output group.
Public methodget_KeyOutputReturns the canonical name of the key output group.
Public methodget_KeyOutputObject
Public methodget_OutputsReturns an array of pointers to IVsOutput2 interfaces providing access to a configuration's output items.
Public methodget_ProjectCfgReturns a pointer to the configuration's IVsProjectCfg2 interface.
Public methodget_PropertyGets the value of a property.
Top

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.

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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft