

Supported language strings (not case sensitive): Visual Studio Branding Package supported controls: Metadata (see Content Metadata Reference): data about the topic, for example, the topic unique ID, keyword value, the topic TOC ID, parent node ID, etc.īody content: compliant with W3C Basic 1.1 XHTML, which includes supported content behaviors (collapsible area, code snippet, etc. To be rendered correctly within the Help Viewer, raw topic content must be W3C Basic 1.1 XHTML. In the event there is no branding package associated with the topic, the Help Viewer will use the fallback branding package located in the Help Viewer application root (Branding_en-US.mshc). See "Creating Branding Package" below for more information about the branding package elements. The branding package contains logos, support for content behaviors, and branding text (copyright, etc.).

When a topic is called for rendering, the Help Viewer gets the branding package elements that are associated with the topic at the time of install or last update, along with the topic XHTML, and combines the two to result in the presented content view (branding data + topic data). This section provides an overview of the components of a presented topic, topic requirements, a short description for how to create a topic (including F1 support requirements) and finally, an example topic with its rendered result. This article contains the following tasks for Visual Studio Help Viewer integrators:Ĭreating a Help Viewer content-branding packageĪdding help to the Visual Studio shell (integrated or isolated)
