VsHierarchyPropID Enumeration

Set this property to true in your project hierarchy if you want your project to always build on debug launch in this case. This ensures that your project is built even if your project is not declared as a build dependency of the startup project. This property is a workaround for the fact that currently there is only support for build dependencies (IVsBuildDependency) and not deploy dependencies in the solution build manager. This property will be used rarely in circumstances where you may have a circular set of dependencies involving a combination of build and deploy dependencies between multiple projects (for example, A has a build dependency on B while B has a deploy dependency on A; if B is the startup project, then solution build manager would not realize it needs to build A to satisfy the required deploy dependency when the above mentioned Tools option is set).

If true, no prompt to save is required before building.

If true, the item is a container (it may not be expandable, but it contains items).

Normally "Deploy" is checked by default if the project supports IVsDeployableProjectCfg.

If true (default) and the project was loaded synchronously, all its dependencies are also loaded synchronously. If false and the project was loaded synchronously, those of its dependencies that support asynchronous load may be loaded asynchronously.

The value of this property is derived from VSDESIGNER_FUNCTIONVISIBILITY.

The value of this property derives from the VSDESIGNER_VARIABLENAMING enumeration.

If true in your hierarchy, Application Settings design time support in your project is disabled.

If true in your hierarchy, the Data Source Window is disabled.

If true, the plus sign is displayed. If false, the plus sign is not displayed.

If true, the node is currently expanded. If false, the node is not expanded. If this property starts as false, the UIHierarchyWindow will update.

If not supported, then a default implementation is provided.

If true, the project handles its own unload and reload. If false (default), the environment handles the unload and reload.

Your hierarchy should support IconHandle or IconImgList/ IconIndex, but not both.

If Expandable is true, then IconIndex+1 is used for the open icon.

If true, Find In Files runs in the main thread.

If true, project storage is local. IPersistFileFormat is used for saving a project regardless of whether it is a local "file" or not.

If true, the item cannot be searched for or replaced. This property should be true for the project file.

If true, the document should be kept alive.

If true, the hierarchy does not want nested hierarchies sorted first and items after, and sorted alphabetically.

The value of this property derives from the VSOVERLAYICON enumeration.

A Project Designer that shows configuration-independent and configuration-dependent property pages in a flat list should use this order as the preferred order for the pages. A project that uses the standard property page frame can ignore this property because the property page frame does not mix the two types of pages in a flat list.

If this property is not supported and the hierarchy implements IVsProject, the provisional viewing status is determined by calling GetProvisionalViewingStatusForFile with the name returned by GetMkDocument.

If true, the file on disk was not last written by the project and thus the user should be prompted to reload due to an external change to the file. This property is defined for ITEMID_ROOT. It is expected that this property is only called during a FilesChanged event handler. The expected implementation is for projects to record the timestamp on the project file when the file is saved. Later when this property is requested, the project should compare the current timestamp of the file to the last recorded save timestamp. If they are not equal then return true, else return false (that is, a reload is not required).

This property is needed so the shell (that is, the File->Save menu item) can display the name in the UI.

If true, the project supports service references.

If true, the project is shown in the list.

This text in this property is displayed while the given hierarchy is the active hierarchy. VT_EMPTY clears hierarchy scoped text and resets to the global text specified by the application.

The property-page that exposes information about My.Application can use this list to determine which values appear in the application-type dropdown as selectable choices for the user. The current list of supported values for Visual Basic's implementation is:

• WindowsApp - a Windows executable with support for Windows application concepts such as My.Forms.

• WindowsClassLib - a DLL with support for Windows application concepts such as My.Forms.

• CommandLineApp - a command-line executable.

• WindowsService - an executable that can be run as a Windows service.

• WebControl - a DLL with support for Web application concepts.

An example value that supports all types is "WindowsApp;WindowsClassLib;CommandLineApp;WindowsService;WebControl".

Set this property to true in your project hierarchy if your Web project supports being consumed by Silverlight.

Set this property to true in your project hierarchy to enable LINQ to DataSet. Setting this property to true generates typed datasets with data tables that inherit from System.Data.TypedTableBase in order to enable LINQ queries.

If true, the project uses a Project Designer Editor.

The format of the target framework moniker is "<Identifier>,Version=<ver>,Profile=<value>" (for example, ".NETFramework,Version=v3.5,Profile=Client").

Examples are “Windows”, “Windows Phone”, “Windows Azure”, “XBox 360”, and “Portable”.