Developer Solutions for Web and Other

The following XML file is used in combination with the XSLT file posted in an earlier post. These 2 files transform into HMTL that views correctly in Visual Studio 2010 HelpViewer 1.0. <? xml   version = " 1.0 "   encoding = " iso-8859-1 " ?> <? xml-stylesheet   type="text/xsl" href="../xslt/gravity.xslt" ?> < HelpDocument >   < Meta >     < title > Add </ title >     < metaTitle > Add </ metaTitle >     < metaID > Help3-7F3D2D9D-Add </ metaID >     < metaParent > Help3-7F3D2D9D-Entity </ metaParent >          < metaKeywords >       < metaKeyword >         < keyword > Add </ keyword >       </ metaKeyword >   ...

This XSL/XSLT file is based on a Visual Studio Help file found in "C:\ProgramData\Microsoft\HelpLibrary\content\Microsoft\store\Development_Frameworks_21823146_VS_100_en-us_9.msha" I've stripped out the content and replaced with  < xsl:if   gt; etc. The values for this content are taken from XML files which have the corresponding XML element hierachy, e.g

To convert XML to HTML you need an XSL (XSLT) file and some application to transform the XML to HTML using this XSL file. Usually this work is done by the browser, by including a link to the XSL file in the XML file, when you open the file in a browser it runs the transform on the XML using the XSL file you've pointed to. But I wanted to run this as a seperate step from a batch file so that I can create my .html files on disk but maintain their content using XML. Here's how I've done it: using   System ; using   System . Collections . Generic ; using   System . Linq ; using   System . Text ; using   System . Xml . Xsl ; using   System . IO ; namespace   Tool . XMLToHTML {      class   Program     {          ///   <summary>          ///  "Help\Help3\_HelpSource\gravity.xslt" "Help\Help3\_HelpSource"...

Recently I've been working with our legacy HTML help files, trying to add them the the new Visual Studio 2010 HelpViewer. This is not a simple task. We wanted the styling of our html to be the same as .NET help files We would also like there to be little or no maintenance required to keep them up to date with the latest Visual Studio Help Styles etc. We have a custom development language so the code snippets require their own color coding and the Language should be "Gravity" and not C# or VB. The content itself should be easily maintained. Our own applications logos and copyright should appear instead of Visual Studios. The requirements above proved to be not a simple to implement as you might think. Below I'll mention the snags I came across and describe how I overcame them. 1. Styling: The styling information was not simple to find, there are documents on http://www.helpware.net/mshelp3/intro.htm which explain some of the content of the help files, this is...