Microsoft.VisualStudio.Shell.Interop.12.1.DesignTime

Opens the .appxmanifest designer displaying the specified tab with the given document handle.

The document handle The tab to display. The HRESULT.

Opens the .appxmanifest designer.

The document handle. The tab to display. The HRESULT.

Opens the .appxmanifest file.

The current project. The document handle. The .appxmanifest document. The HRESULT.

Opens the .appxmanifest file.

The project. Determines whether to force save the document. The document handle. The .appxmanifest file. The HRESULT.

Subscribes to bootstrapper events.

The event sink. The event cookie.

Asynchronously bootstraps the given target

The name of the project. The target. The items. The packages to download. An optional callback to receive output messages. An IVsTask whose result is an instance of IVsAppContainerBootstrapperResult, or an error code. This is E_ABORT if called on the main thread and an advised callback has aborted the operation; otherwise S_OK.

Asynchronously bootstraps given target and established debugger host for debugging the app represented by the recipe.

The name of the project. The target. The path of the recipe. An optional callback to receive output messages. An IVsTask whose result is an instance of IVsAppContainerBootstrapperResult, or an error code. This is E_ABORT if called on the main thread and an advised callback has aborted the operation; otherwise S_OK.

Asynchronously bootstraps given target and established diagnostics host for debugging the app represented by the recipe.

The name of the project. The target. The items. The packages to download. An optional callback to receive output messages. An IVsTask whose result is an instance of IVsAppContainerBootstrapperResult, or an error code. This is E_ABORT if called on the main thread and an advised callback has aborted the operation; otherwise S_OK.

Unsubscribes from bootstrapper events.

The event cookie.

Enables a client to be notified of app container deployment events.

[in] The event sink to call when an app container deployment event occurs. A cookie associated with the given interface.

Initiates deployment of the app container application on the local machine. It creates a "layout folder" containing the app files as defined in the package recipe file and registers the application with Windows package manager. After successfully executing of this process, the application is ready to be launched on the local box or on the simulator.

[in] The deployment options for this instance of the app container application. [in] The package recipe file that defines the package contents. [in] The location where the app container application is deployed. [in] The unique name of the project. [in] The callback routine that is to be notified when events occur. The app container application deployed on the local machine.

Initiate deployment of the app container application on a remote machine.

[in] The deployment options for this instance of the app container application. [in] The protocol used to interact with the remote machine. [in] The package recipe file that defines the package contents. [in] The unique name of the project. [in] The callback routine that is to be notified when events occur. The app container application deployed on the remote machine.

Initiate deployment of the app container application on a remote machine.

[in] The deployment options for this instance of the app container application. [in] The protocol used to interact with the remote machine. The target. [in] The package recipe file that defines the package contents. [in] The unique name of the project. [in] The callback routine that is to be notified when events occur. The app container application deployed on the remote machine.

Disables clients from receiving notifications of app container deployment events.

The event cookie.

Subscribes to build property storage events.

The event sink. [out] The event cookie. The HRESULT.

Unsubscribes from build property storage events.

The event cookie. The HRESULT.

Occurs when certain items have changed.

The items. An array containing the full paths of the items. The HRESULT.

Gets the enumerator.

The enumerator.

Determines whether the specified document is in a project.

The path of the document. [out] if the document is found in the project, otherwise . [out] The priority. For a list of known priority values, see. [out] The item ID of the document. The HRESULT.

Occurs before unloaded projects are reloaded by the user. The implementer of this event sink is expected to return the list of additional files that need to be closed before the projects can be reloaded. The unloaded projects' project files are already known to be closed and need not be included in the list that is returned by this method. The implementer does not need to look the files up in the Running Document Table to see if they are actually open. Visual Studio makes sure that the files are actually open in an editor (i.e. not registered in the RDT with the RDT_ProjSlnDocument flag set). These additional files are typically files imported or included by the unloaded project files that must be available in order for the reloading projects to open.

The number of projects to be reloaded. An array of ProjectID GUIDs of unloaded projects to be reloaded. An array of the names of files to be closed.

Subscribes to the shared project's events.

The event sink. The event cookie.

Enumerates the projects that import the project file that this Shared Assets Project imports and owns.

The HRESULT.

Stops subscribing to shared asset project events.

The event cookie.

Notifies listening clients that a project is being loaded, and it imports the project file that this Shared Assets Project imports and owns.

The project. The HRESULT.

Notifies listening clients that a project is being removed or unloaded, and it imports the project file that this Shared Assets Project imports and owns.

The GUID of the project. The HRESULT.

Adds an existing project to the solution.

The full path of the project. [optional] The parent IVsHierarchy element under which to create the new project. This can be the solution folder or any project that implements IVsParentProject3. [out] The new IVsHierarchy element. The HRESULT.

Adds a new project to the solution, using a project template.

The path of the template. [optional] Custom keywords to pass to the template engine. Strings must have the form "keyword=value". [optional] The target framework (if applicable) for template selection. The location on disk where the project will be created. The name of the project. [optional] The parent project under which to create the new project. This can be solution folder or any project that implements IVsParentProject3. The newly created project. If the template creates more than one project, this one is the first one created.

Uses the open project dialog to select a project.

[optional] The title of the dialog. [optional] The initial location on disk from which to open the AddExistingProject dialog. [optional] The preferred project type. If this is , "Any projects" is selected by default. [out] If project creation is successful, the name of selected project file. The HRESULT.

Sets the parent of the project. The solution considers to be a child (in a nested hierarchy) of , and it does not enumerate it in the solution hierarchy. The hierarchy is responsible for adding a visual representation of this project in Solution Explorer. is expected to implement IVsParentProject3, otherwise this method does nothing.

The IVsHierarchy element of the project. The IVsHierarchy element of the project's parent. The HRESULT.

The notification that is fired during project creation, after the solution has registered the project file in the RunningDocumentTable. This event can be used to find out the value that was assigned to the project in the RDT. Note: If the solution's call to RegisterAndLockDocument failed, then will be VSCOOKIE_NIL. Clients of this event are expected to explicitly recognize this case and react accordingly. For example, a client may want to re-register their project placeholder document in the RDT.

The project ID. The full path of the project file. The doc cookie in the RunningDocumentTable. The HRESULT.

A notification fired during project creation, before the solution attempts to register the project file in the RunningDocumentTable. This event can be used to find out when to unregister a project placeholder document from the RDT so as to not block the opening of the real project.

The project ID. The full path of the project file. The HRESULT.

Gets the number of IVsHierarchy objects.

The number of IVsHierarchy objects.

Gets the specified IVsHierarchy object.

The index of the IVsHierarachy object. The IVsHierarchy object.

Gets the full path of the shared items.

The full path of the shared items.

Determines whether to add a new virtual project to the Project window.

Reload the project when the project file changes.

Used to discriminate in more detail between the priorities of items in a project. It is used by to determine the best project to open a file. If you want your projects to express this detailed priority value, you should implement in addition to implementing .

The document is intrinsic.

The document is standard.

The document is an indirect member (an item being imported from another project file).

The document is a non-member.

The document can be added as a non-member.

The document is external.

The document can be added as external.

The document is unsupported.

Specifies properties of the Visual Studio shell.

VT_BOOL [optional] If this returns , this item is imported from another project file that is shared across projects. Otherwise it returns . A shared item is special. It is added to this importing project hierarchy as a hidden linked file, so it is enumerable via and , but it cannot be mutated by this importing project.

VT_UNKNOWN [optional] Gets or sets the contextual IVsHierarchy for the items that are shared by other projects. It is used for sharing scenarios, for example, when a document is shared across projects. When someone edits that document, one project must be selected as the context to offer to IntelliSense. The currently-selected project hierarchy could be retrieved or changed via this property on the master owning project hierarchy. Note this property is per-project in the current implementation, GetProperty/SetProperty must be invoked on the root node.

VT_BSTR [optional] The short version of VSHPROPID_Subcaption.

VT_BSTR [optional] Provides a vertical bar ('|') delimited list of the full paths of the "Shared.items" project files that have been imported by the project. Note: This property does not return "Shared.items" files for Shared Folder nodes that manage their shared MSBuild file as a nested hierarchy implementation.

VT_BSTR [optional] Provides a space-delimited list of project tree node capabilities. Note: Unlike VSHPROPID_ProjectCapabilities, which is available only on the Project Root node, this property is allowed on every node.

VT_BSTR [optional] Gets the deployment relative path of the given item. The deployment relative path is the file location relative to the package directory, when the given file is deployed.

VT_BOOL [optional] Returns if the given item represents the folder node as an ancestor of shared items.

VT_BSTR [optional] Returns the "one app" capabilities. When they include "Migration" or "Add Platform", they are used to pick the right template using ApplyTo metadata from templates.

VT_UNKNOWN [optional] Returns the implementation of IVsMSBuildImportsStorage for a project.

VT_UNKNOWN [optional] Returns the actual owning shared project hierarchy of the given shared item. Note: The item ID should be the ID of a shared item. If the given item is already an item in a shared assets project, then it returns this shared assets project.

VT_UNKNOWN [optional] Returns the implementation of IVsSharedAssetsProject for the given shared project hierarchy. The item ID should be VSITEMID_ROOT.

VT_BOOL [optional] Returns if the given item represents the MSBuild file that imports the shared items.

VT_BOOL [optional] Returns if the given project wants to be excluded from participating with cmdidMoveFileToProjectXXX commands.

VT_I4 [optional] Returns a that determines whether the given project can perform building via . This property can be used as a quick test to know if build-related features should be enabled.The absence of this property is equivalent to returning : the caller must call to see if building is possible. : feature is always enabled; : feature is enabled now; : feature is not enabled now; : feature is not implemented. Returning QCA_Never/No does not stop all callers from accessing and using the project's interface.

VT_I4 [optional] Returns a regarding if the given project can perform F5 debug launch via .The absence of this property is equivalent to returning : the caller must call to see if building is possible. : feature is always enabled; : feature is enabled now; : feature is not enabled now; : feature is not implemented. Returning QCA_Never/No does not stop all callers from accessing and using the project's interface.

T_I4 [optional] Returns a that determines whether the given project can perform deploying via .The absence of this property is equivalent to returning : the caller must call to see if building is possible. : feature is always enabled; : feature is enabled now; : feature is not enabled now; : feature is not implemented. Returning QCA_Never/No does not stop all callers from accessing and using the project's interface.

Specifies when a feature is enabled.

The feature is always enabled.

The feature is enabled now.

The caller must call to see if deployment is possible.

The feature is not enabled now.

The feature is not implemented.

Specifies the app manifest designer tab to be opened by the method.

Opens the Current tab in the app manifest designer.

Opens the Application UI tab in the app manifest designer.

Opens the Capabilities tab in the app manifest designer.

Opens the Declarations tab in the app manifest designer.

Opens the Content URIs tab in the app manifest designer.

Opens the Packaging tab in the app manifest designer.

Opens the Hardware Requirements tab in the app manifest designer.

Provides programmatic access to a project's .appxmanifext file. You can use it to open a DocData object provided by the Manifest Designer, ensure that it is registered in the running document table (RDT), and return a document handle object that implements two interfaces: IVsDocumentLockHolder and IVsInvisibleEditor. This forces any existing document window to close, and causes the returned document handle to hold a RDT_EditLock. When you need to keep the document handle for longer periods of time, cast it to IVsInvisibleEditor and use GetDocData to get a pointer to a fresh object model. When finished with the document handle, always call IVsDocumentLockHolder.CloseDocumentHolder(), usually passing (uint)__FRAMECLOSE.FRAMECLOSE_SaveIfDirty as the save option.

Represents the bootstrapper.

Deploys the app container application.

Implemented by the project system to give flavors access to the MSBuild property system. This interface provides more flexibility around setting properties than . It allows for adding a new conditional property group and does not escape the values.

Represents build property storage events.

Provides an enumeration for objects.

Provides the ability to determine whether a document is in a project.

Implemented by clients that coordinate files required for loading projects.You subscribe to these events via IVsSolution::AdviseSolutionEvents.

Represents a project with shared assets.

Represents the events associated with projects that have shared assets.

Provides top-level manipulation or maintenance of the solution.

Provides events associated with solutions.

A project hierarchy with shared MSBuild files. In the Save Changes dialog, this project file appears with the name "[Shared MSBuild Project Files]". This node appears in the Save Changes dialog when there are shared MSBuild files that need to be saved and the files do not have affinity to a particular shared assets project. A new singleton instance of this hierarchy is created (if necessary) for each solution and closed when the solution closes. This singleton hierarchy always has the same value as its property. The SharedMSBuildFilesManagerHierarchy project supports the and properties for each of its shared MSBuild file project items.