SHFB Wiki & Documentation Rss Feedhttp://www.codeplex.com/Wiki/View.aspx?ProjectName=SHFB&title=HomeSHFB Wiki Rss DescriptionUpdated Wiki: Homehttps://shfb.codeplex.com/wikipage?version=48<div class="wikidoc"><h1>PLEASE NOTE: THIS PROJECT HAS BEEN MOVED TO GITHUB</h1>
<a href="https://github.com/EWSoftware/SHFB">https://github.com/EWSoftware/SHFB</a><br /><br />Do not file any further issues here on CodePlex. If you have an issue or a question, please submit it on the Issues page on the <a href="https://github.com/EWSoftware/SHFB/issues">GitHub project site</a>.<br /></div><div class="ClearBoth"></div>EWoodruffMon, 26 Jan 2015 23:08:20 GMTUpdated Wiki: Home 20150126110820PUpdated Wiki: Documentationhttps://shfb.codeplex.com/documentation?version=14<div class="wikidoc"><h1>PLEASE NOTE: THIS PROJECT HAS BEEN MOVED TO GITHUB</h1>
<a href="https://github.com/EWSoftware/SHFB">https://github.com/EWSoftware/SHFB</a><br /><br />Wiki Content: <a href="https://github.com/EWSoftware/SHFB/wiki">https://github.com/EWSoftware/SHFB/wiki</a><br /><br />Do not file any further issues here on CodePlex. If you have an issue or a question, please submit it on the Issues page on the <a href="https://github.com/EWSoftware/SHFB/issues">GitHub project site</a>.<br />
<h2>Installation and Usage</h2>
Download the <a href="http://shfb.codeplex.com/releases">latest release</a>, extract it to a folder, and then run <b>SandcastleInstaller.exe</b> to run the guided installation of Sandcastle, the various extra items from the Sandcastle Styles project, and the Sandcastle Help File Builder.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> topic for more information about the required set of additional tools.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project. A full copy of the help file is also included with the installer and a shortcut to it can be found in the <i>Sandcastle Help File Builder</i> folder in the <i>Start | All Programs</i> menu.<br />
<h2>Viewing Downloaded Help Files</h2>
The help files contained in the project downloads may need to be unblocked before you can view their content. If you do not see any information in the content pane after opening a help file, do the following:<br />
<ul><li>Copy the help file to your hard drive and open it from there. Trying to view a help file from a network share can cause the content to be blocked.</li>
<li>If a security dialog appears asking if you want to open the file, uncheck the &quot;Always ask before opening this file&quot; checkbox.</li>
<li>If the file is still blocked, open Windows Explorer, right-click the CHM file, select <b>Properties</b>, and then click the <b>Unblock</b> option.</li>
<li>Apply the file property changes and open the help file again.</li></ul>
<h2>Online Help and Guides</h2>
<ul><li><a href="http://www.ewoodruff.us/shfbdocs">Sandcastle Help File Builder</a></li>
<li><a href="http://www.ewoodruff.us/sandcastletools">Sandcatle Tools</a></li>
<li><a href="http://www.ewoodruff.us/mamlguide">Sandcastle MAML Guide</a></li>
<li><a href="http://www.ewoodruff.us/xmlcommentsguide">Sandcastle XML Comments Guide</a></li></ul>
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Documentation">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/ac8e467d-c0aa-4a6d-9690-73d148f67bc7.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /><br /><br /><a href="http://www.e-iceblue.com/Introduce/word-for-net-introduce.html?aff_id=28&amp;amp;amp;banner_id=10"><img style="border:none;" src="http://www.e-iceblue.com/components/com_affiliate/banners/0cd241c559dade9442198ec445cbc4cf.gif" alt="E-IceBlue Ad" title="E-IceBlue Ad" /></a></div><div class="ClearBoth"></div>EWoodruffMon, 26 Jan 2015 21:48:44 GMTUpdated Wiki: Documentation 20150126094844PUpdated Wiki: Documentationhttps://shfb.codeplex.com/documentation?version=13<div class="wikidoc"><h2>Installation and Usage</h2>
Download the <a href="http://shfb.codeplex.com/releases">latest release</a>, extract it to a folder, and then run <b>SandcastleInstaller.exe</b> to run the guided installation of Sandcastle, the various extra items from the Sandcastle Styles project, and the Sandcastle Help File Builder.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> topic for more information about the required set of additional tools.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project. A full copy of the help file is also included with the installer and a shortcut to it can be found in the <i>Sandcastle Help File Builder</i> folder in the <i>Start | All Programs</i> menu.<br />
<h2>Viewing Downloaded Help Files</h2>
The help files contained in the project downloads may need to be unblocked before you can view their content. If you do not see any information in the content pane after opening a help file, do the following:<br />
<ul><li>Copy the help file to your hard drive and open it from there. Trying to view a help file from a network share can cause the content to be blocked.</li>
<li>If a security dialog appears asking if you want to open the file, uncheck the &quot;Always ask before opening this file&quot; checkbox.</li>
<li>If the file is still blocked, open Windows Explorer, right-click the CHM file, select <b>Properties</b>, and then click the <b>Unblock</b> option.</li>
<li>Apply the file property changes and open the help file again.</li></ul>
<h2>Online Help and Guides</h2>
<ul><li><a href="http://www.ewoodruff.us/shfbdocs">Sandcastle Help File Builder</a></li>
<li><a href="http://www.ewoodruff.us/sandcastletools">Sandcatle Tools</a></li>
<li><a href="http://www.ewoodruff.us/mamlguide">Sandcastle MAML Guide</a></li>
<li><a href="http://www.ewoodruff.us/xmlcommentsguide">Sandcastle XML Comments Guide</a></li></ul>
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Documentation">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/ac8e467d-c0aa-4a6d-9690-73d148f67bc7.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /><br /><br /><a href="http://www.e-iceblue.com/Introduce/word-for-net-introduce.html?aff_id=28&amp;amp;amp;banner_id=10"><img style="border:none;" src="http://www.e-iceblue.com/components/com_affiliate/banners/0cd241c559dade9442198ec445cbc4cf.gif" alt="E-IceBlue Ad" title="E-IceBlue Ad" /></a></div><div class="ClearBoth"></div>EWoodruffSun, 10 Aug 2014 20:28:33 GMTUpdated Wiki: Documentation 20140810082833PUpdated Wiki: Homehttps://shfb.codeplex.com/wikipage?version=47<div class="wikidoc"><h2>Welcome to the Sandcastle Help File Builder Project</h2>
This project is composed of two separate parts that work together: the Sandcastle tools and the Sandcastle Help File Builder. The Sandcastle tools are used to create help files for managed class libraries containing both conceptual and API reference topics. API reference topics are created by combining the XML comments that are embedded in your source code with the syntax and structure of the types which is acquired by reflecting against the associated .NET Framework assembly. Conceptual topics are created by converting XML documents that you author containing Microsoft Assistance Markup Language (MAML). The Sandcastle tools are command-line based and have no GUI front-end, project management features, or an automated build process.<br /><br />The Sandcastle Help File Builder was created to fill in the gaps, provide the missing NDoc-like features that are used most often, and provide standalone GUI and command line based tools to build a help file in an automated fashion. A Visual Studio integration package is also available for it so that help projects can be created and managed entirely from within Visual Studio.<br /><br />Sandcastle was originally created by Microsoft back in 2006. The last official release from Microsoft occurred in June 2010. Until October 2012, it was hosted at the Sandcastle project site on CodePlex. In October 2012, Microsoft officially declared that they were ceasing support and development of Sandcastle. The Sandcastle tools have been merged into the Sandcastle Help File Builder project and all future development and support for them will be handled at this project site. The Sandcastle tools themselves remain separate from and have no dependency on the help file builder. As such, they can be used in a standalone fashion with your own scripts and build tools if that is your preference.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> for information about the required set of additional tools that need to be installed, where to get them, and how to make sure everything is configured correctly. The guided installer also provides information on the necessary tools and walks you through the installation steps.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project.<br />
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Home">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/ac8e467d-c0aa-4a6d-9690-73d148f67bc7.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /><br /><br /><a href="http://www.e-iceblue.com/Introduce/word-for-net-introduce.html?aff_id=28&amp;amp;amp;banner_id=10"><img style="border:none;" src="http://www.e-iceblue.com/components/com_affiliate/banners/0cd241c559dade9442198ec445cbc4cf.gif" alt="E-IceBlue Ad" title="E-IceBlue Ad" /></a></div><div class="ClearBoth"></div>EWoodruffSun, 10 Aug 2014 20:27:41 GMTUpdated Wiki: Home 20140810082741PUpdated Wiki: Homehttps://shfb.codeplex.com/wikipage?version=46<div class="wikidoc"><h2>Welcome to the Sandcastle Help File Builder Project</h2>
This project is composed of two separate parts that work together: the Sandcastle tools and the Sandcastle Help File Builder. The Sandcastle tools are used to create help files for managed class libraries containing both conceptual and API reference topics. API reference topics are created by combining the XML comments that are embedded in your source code with the syntax and structure of the types which is acquired by reflecting against the associated .NET Framework assembly. Conceptual topics are created by converting XML documents that you author containing Microsoft Assistance Markup Language (MAML). The Sandcastle tools are command-line based and have no GUI front-end, project management features, or an automated build process.<br /><br />The Sandcastle Help File Builder was created to fill in the gaps, provide the missing NDoc-like features that are used most often, and provide standalone GUI and command line based tools to build a help file in an automated fashion. A Visual Studio integration package is also available for it so that help projects can be created and managed entirely from within Visual Studio.<br /><br />Sandcastle was originally created by Microsoft back in 2006. The last official release from Microsoft occurred in June 2010. Until October 2012, it was hosted at the Sandcastle project site on CodePlex. In October 2012, Microsoft officially declared that they were ceasing support and development of Sandcastle. The Sandcastle tools have been merged into the Sandcastle Help File Builder project and all future development and support for them will be handled at this project site. The Sandcastle tools themselves remain separate from and have no dependency on the help file builder. As such, they can be used in a standalone fashion with your own scripts and build tools if that is your preference.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> for information about the required set of additional tools that need to be installed, where to get them, and how to make sure everything is configured correctly. The guided installer also provides information on the necessary tools and walks you through the installation steps.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project.<br />
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Home">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/ac8e467d-c0aa-4a6d-9690-73d148f67bc7.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /></div><div class="ClearBoth"></div>EWoodruffSun, 18 May 2014 02:20:23 GMTUpdated Wiki: Home 20140518022023AUpdated Wiki: Documentationhttps://shfb.codeplex.com/documentation?version=12<div class="wikidoc"><h2>Installation and Usage</h2>
Download the <a href="http://shfb.codeplex.com/releases">latest release</a>, extract it to a folder, and then run <b>SandcastleInstaller.exe</b> to run the guided installation of Sandcastle, the various extra items from the Sandcastle Styles project, and the Sandcastle Help File Builder.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> topic for more information about the required set of additional tools.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project. A full copy of the help file is also included with the installer and a shortcut to it can be found in the <i>Sandcastle Help File Builder</i> folder in the <i>Start | All Programs</i> menu.<br />
<h2>Viewing Downloaded Help Files</h2>
The help files contained in the project downloads may need to be unblocked before you can view their content. If you do not see any information in the content pane after opening a help file, do the following:<br />
<ul><li>Copy the help file to your hard drive and open it from there. Trying to view a help file from a network share can cause the content to be blocked.</li>
<li>If a security dialog appears asking if you want to open the file, uncheck the &quot;Always ask before opening this file&quot; checkbox.</li>
<li>If the file is still blocked, open Windows Explorer, right-click the CHM file, select <b>Properties</b>, and then click the <b>Unblock</b> option.</li>
<li>Apply the file property changes and open the help file again.</li></ul>
<h2>Online Help and Guides</h2>
<ul><li><a href="http://www.ewoodruff.us/shfbdocs">Sandcastle Help File Builder</a></li>
<li><a href="http://www.ewoodruff.us/sandcastletools">Sandcatle Tools</a></li>
<li><a href="http://www.ewoodruff.us/mamlguide">Sandcastle MAML Guide</a></li>
<li><a href="http://www.ewoodruff.us/xmlcommentsguide">Sandcastle XML Comments Guide</a></li></ul>
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Documentation">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/ac8e467d-c0aa-4a6d-9690-73d148f67bc7.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /></div><div class="ClearBoth"></div>EWoodruffSun, 18 May 2014 02:19:34 GMTUpdated Wiki: Documentation 20140518021934AUpdated Wiki: Future Enhancements and Featureshttps://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=17<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread-safe though. Possible changes and issues:
<ul><li>Add a configuration property to enable parallel builds but default to the current synchronous build behavior.</li>
<li>All build components would need an overriden virtual property to indicate if they support parallel execution. The default if not overridden would be false. Each build component and syntax generator would need checking to make sure it is thread-safe. For components that contain nested components, they would need to check each nested component too.</li>
<li>Concurrent updates to static members. Use thread-safe constructs where needed.</li>
<li>Use of non-thread-safe objects like the code colorizer. Wrap them in ThreadLocal&lt;T&gt;?</li>
<li>Copying of content files. Track source and destination files to copy in thread-safe constructs. Then, when the component is disposed of, copy the content.</li>
<li><a href="http://shfb.codeplex.com/workitem/33859">http://shfb.codeplex.com/workitem/33859</a></li></ul></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffSun, 18 May 2014 02:15:57 GMTUpdated Wiki: Future Enhancements and Features 20140518021557AUpdated Wiki: Documentationhttps://shfb.codeplex.com/documentation?version=11<div class="wikidoc"><h2>Installation and Usage</h2>
Download the <a href="http://shfb.codeplex.com/releases">latest release</a>, extract it to a folder, and then run <b>SandcastleInstaller.exe</b> to run the guided installation of Sandcastle, the various extra items from the Sandcastle Styles project, and the Sandcastle Help File Builder.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> topic for more information about the required set of additional tools.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project. A full copy of the help file is also included with the installer and a shortcut to it can be found in the <i>Sandcastle Help File Builder</i> folder in the <i>Start | All Programs</i> menu.<br />
<h2>Viewing Downloaded Help Files</h2>
The help files contained in the project downloads may need to be unblocked before you can view their content. If you do not see any information in the content pane after opening a help file, do the following:<br />
<ul><li>Copy the help file to your hard drive and open it from there. Trying to view a help file from a network share can cause the content to be blocked.</li>
<li>If a security dialog appears asking if you want to open the file, uncheck the &quot;Always ask before opening this file&quot; checkbox.</li>
<li>If the file is still blocked, open Windows Explorer, right-click the CHM file, select <b>Properties</b>, and then click the <b>Unblock</b> option.</li>
<li>Apply the file property changes and open the help file again.</li></ul>
<h2>Online Help and Guides</h2>
<ul><li><a href="http://www.ewoodruff.us/shfbdocs">Sandcastle Help File Builder</a></li>
<li><a href="http://www.ewoodruff.us/sandcastletools">Sandcatle Tools</a></li>
<li><a href="http://www.ewoodruff.us/mamlguide">Sandcastle MAML Guide</a></li>
<li><a href="http://www.ewoodruff.us/xmlcommentsguide">Sandcastle XML Comments Guide</a></li></ul>
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Documentation">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/bd1ddb51-1c4f-434f-bb1a-ce2135d3a909.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /></div><div class="ClearBoth"></div>EWoodruffSun, 18 May 2014 01:20:56 GMTUpdated Wiki: Documentation 20140518012056AUpdated Wiki: Homehttps://shfb.codeplex.com/wikipage?version=45<div class="wikidoc"><h2>Welcome to the Sandcastle Help File Builder Project</h2>
This project is composed of two separate parts that work together: the Sandcastle tools and the Sandcastle Help File Builder. The Sandcastle tools are used to create help files for managed class libraries containing both conceptual and API reference topics. API reference topics are created by combining the XML comments that are embedded in your source code with the syntax and structure of the types which is acquired by reflecting against the associated .NET Framework assembly. Conceptual topics are created by converting XML documents that you author containing Microsoft Assistance Markup Language (MAML). The Sandcastle tools are command-line based and have no GUI front-end, project management features, or an automated build process.<br /><br />The Sandcastle Help File Builder was created to fill in the gaps, provide the missing NDoc-like features that are used most often, and provide standalone GUI and command line based tools to build a help file in an automated fashion. A Visual Studio integration package is also available for it so that help projects can be created and managed entirely from within Visual Studio.<br /><br />Sandcastle was originally created by Microsoft back in 2006. The last official release from Microsoft occurred in June 2010. Until October 2012, it was hosted at the Sandcastle project site on CodePlex. In October 2012, Microsoft officially declared that they were ceasing support and development of Sandcastle. The Sandcastle tools have been merged into the Sandcastle Help File Builder project and all future development and support for them will be handled at this project site. The Sandcastle tools themselves remain separate from and have no dependency on the help file builder. As such, they can be used in a standalone fashion with your own scripts and build tools if that is your preference.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> for information about the required set of additional tools that need to be installed, where to get them, and how to make sure everything is configured correctly. The guided installer also provides information on the necessary tools and walks you through the installation steps.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project.<br />
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="https://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Home">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/html/bd1ddb51-1c4f-434f-bb1a-ce2135d3a909.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /></div><div class="ClearBoth"></div>EWoodruffSun, 18 May 2014 01:18:59 GMTUpdated Wiki: Home 20140518011859AUpdated Wiki: Future Enhancements and Featureshttps://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=16<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread-safe though. Possible changes and issues:
<ul><li>Add a configuration property to enable parallel builds but default to the current synchronous build behavior.</li>
<li>All build components would need an overriden virtual property to indicate if they support parallel execution. The default if not overridden would be false. Each build component and syntax generator would need checking to make sure it is thread-safe. For components that contain nested components, they would need to check each nested component too.</li>
<li>Concurrent updates to static members. Use thread-safe constructs where needed.</li>
<li>Use of non-thread-safe objects like the code colorizer. Wrap them in ThreadLocal&lt;T&gt;?</li>
<li>Copying of content files. Track source and destination files to copy in thread-safe constructs. Then, when the component is disposed of, copy the content.</li>
<li><a href="http://shfb.codeplex.com/workitem/33859">http://shfb.codeplex.com/workitem/33859</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffMon, 10 Mar 2014 02:21:04 GMTUpdated Wiki: Future Enhancements and Features 20140310022104AUpdated Wiki: Future Enhancements and Featureshttps://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=15<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread-safe though. Possible changes and issues:
<ul><li>Add a configuration property to enable parallel builds but default to the current synchronous build behavior.</li>
<li>All build components would need an overriden virtual property to indicate if they support parallel execution. The default if not overridden would be false. Each build component and syntax generator would need checking to make sure it is thread-safe. For components that contain nested components, they would need to check each nested component too.</li>
<li>Concurrent updates to static members. Use thread-safe constructs where needed.</li>
<li>Use of non-thread-safe objects like the code colorizer. Wrap them in ThreadLocal&lt;T&gt;?</li>
<li>Copying of content files. Track source and destination files to copy in thread-safe constructs. Then, when the component is disposed of, copy the content.</li>
<li><a href="http://shfb.codeplex.com/workitem/33859">http://shfb.codeplex.com/workitem/33859</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffMon, 13 Jan 2014 03:36:33 GMTUpdated Wiki: Future Enhancements and Features 20140113033633AUpdated Wiki: Future Enhancements and Featureshttps://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=14<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread-safe though. Possible changes and issues:
<ul><li>Add a configuration property to enable parallel builds but default to the current synchronous build behavior.</li>
<li>All build components would need an overriden virtual property to indicate if they support parallel execution. The default if not overridden would be false. Each build component and syntax generator would need checking to make sure it is thread-safe. For components that contain nested components, they would need to check each nested component too.</li>
<li>Concurrent updates to static members. Use thread-safe constructs where needed.</li>
<li>Use of non-thread-safe objects like the code colorizer. Wrap them in ThreadLocal&lt;T&gt;?</li>
<li>Copying of content files. Track source and destination files to copy in thread-safe constructs. Then, when the component is disposed of, copy the content.</li>
<li><a href="http://shfb.codeplex.com/workitem/33859">http://shfb.codeplex.com/workitem/33859</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffThu, 05 Dec 2013 03:48:05 GMTUpdated Wiki: Future Enhancements and Features 20131205034805AUpdated Wiki: Future Enhancements and Featureshttps://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=13<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread-safe though. Possible changes and issues:
<ul><li>Add a configuration property to enable parallel builds but default to the current synchronous build behavior.</li>
<li>All build components would need an overriden virtual property to indicate if they support parallel execution. The default if not overridden would be false. Each build component and syntax generator would need checking to make sure it is thread-safe. For components that contain nested components, they would need to check each nested component too.</li>
<li>Concurrent updates to static members. Use thread-safe constructs where needed.</li>
<li>Use of non-thread-safe objects like the code colorizer. Wrap them in ThreadLocal&lt;T&gt;?</li>
<li>Copying of content files. Track source and destination files to copy in thread-safe constructs. Then, when the component is disposed of, copy the content.</li>
<li><a href="http://shfb.codeplex.com/workitem/33859">http://shfb.codeplex.com/workitem/33859</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffFri, 04 Oct 2013 01:52:43 GMTUpdated Wiki: Future Enhancements and Features 20131004015243AUpdated Wiki: Future Enhancements and Featureshttp://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=12<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread-safe though. Possible changes and issues:
<ul><li>Add a configuration property to enable parallel builds but default to the current synchronous build behavior.</li>
<li>All build components would need an overriden virtual property to indicate if they support parallel execution. The default if not overridden would be false. Each build component and syntax generator would need checking to make sure it is thread-safe. For components that contain nested components, they would need to check each nested component too.</li>
<li>Concurrent updates to static members. Use thread-safe constructs where needed.</li>
<li>Use of non-thread-safe objects like the code colorizer. Wrap them in ThreadLocal&lt;T&gt;?</li>
<li>Copying of content files. Track source and destination files to copy in thread-safe constructs. Then, when the component is disposed of, copy the content.</li>
<li><a href="http://shfb.codeplex.com/workitem/33859">http://shfb.codeplex.com/workitem/33859</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
<ul><li>Add a transformation to match the SHFB hashed member naming option method. That would get rid of the need to load the reflection file in SHFB after applying the doc model transformation. <a href="http://shfb.codeplex.com/workitem/33233">http://shfb.codeplex.com/workitem/33233</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffMon, 18 Mar 2013 01:52:03 GMTUpdated Wiki: Future Enhancements and Features 20130318015203AUpdated Wiki: Future Enhancements and Featureshttp://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=11<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Investigate improving the performance of BuildAssembler. Things to consider:
<ul><li>Longer term, investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread safe though.</li>
<li><a href="http://shfb.codeplex.com/workitem/33224">http://shfb.codeplex.com/workitem/33224</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
<ul><li>Add a transformation to match the SHFB hashed member naming option method. That would get rid of the need to load the reflection file in SHFB after applying the doc model transformation. <a href="http://shfb.codeplex.com/workitem/33233">http://shfb.codeplex.com/workitem/33233</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffSat, 09 Mar 2013 21:39:13 GMTUpdated Wiki: Future Enhancements and Features 20130309093913PUpdated Wiki: Future Enhancements and Featureshttp://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=10<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Expose as public many of the internal BuildAssembler-related classes used for stuff like target info. That will make it easier to reuse the classes in third-party components and third-party components derived from existing Sandcastle build components. <a href="http://shfb.codeplex.com/workitem/33223">http://shfb.codeplex.com/workitem/33223</a></li></ul>
<ul><li>Investigate improving the performance of BuildAssembler. Things to consider:
<ul><li>Longer term, investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread safe though.</li>
<li><a href="http://shfb.codeplex.com/workitem/33224">http://shfb.codeplex.com/workitem/33224</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
<ul><li>Add a transformation to match the SHFB hashed member naming option method. That would get rid of the need to load the reflection file in SHFB after applying the doc model transformation. <a href="http://shfb.codeplex.com/workitem/33233">http://shfb.codeplex.com/workitem/33233</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffSun, 03 Mar 2013 02:22:48 GMTUpdated Wiki: Future Enhancements and Features 20130303022248AUpdated Wiki: Future Enhancements and Featureshttp://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=9<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>Expose as public many of the internal BuildAssembler-related classes used for stuff like target info. That will make it easier to reuse the classes in third-party components and third-party components derived from existing Sandcastle build components. <a href="http://shfb.codeplex.com/workitem/33223">http://shfb.codeplex.com/workitem/33223</a></li></ul>
<ul><li>Investigate improving the performance of BuildAssembler. Things to consider:
<ul><li>Sharing information between build components that use the same info rather than loading it again.</li>
<li>Use pre-built cache files to save on initialization time.</li>
<li>Use pre-built cache files to load information on demand to reduce memory usage.</li>
<li>Longer term, investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread safe though.</li>
<li><a href="http://shfb.codeplex.com/workitem/33224">http://shfb.codeplex.com/workitem/33224</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
<ul><li>Add a transformation to match the SHFB hashed member naming option method. That would get rid of the need to load the reflection file in SHFB after applying the doc model transformation. <a href="http://shfb.codeplex.com/workitem/33233">http://shfb.codeplex.com/workitem/33233</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffSun, 03 Mar 2013 02:20:48 GMTUpdated Wiki: Future Enhancements and Features 20130303022048AUpdated Wiki: Future Enhancements and Featureshttp://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=8<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>See if there is a way to improve the keyword index in Help 1 and Website output so that member names common to multiple classes are differentiated in the index. <a href="http://shfb.codeplex.com/workitem/32262">http://shfb.codeplex.com/workitem/32262</a></li></ul>
<ul><li>Expose as public many of the internal BuildAssembler-related classes used for stuff like target info. That will make it easier to reuse the classes in third-party components and third-party components derived from existing Sandcastle build components. <a href="http://shfb.codeplex.com/workitem/33223">http://shfb.codeplex.com/workitem/33223</a></li></ul>
<ul><li>Investigate improving the performance of BuildAssembler. Things to consider:
<ul><li>Sharing information between build components that use the same info rather than loading it again.</li>
<li>Use pre-built cache files to save on initialization time.</li>
<li>Use pre-built cache files to load information on demand to reduce memory usage.</li>
<li>Longer term, investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread safe though.</li>
<li><a href="http://shfb.codeplex.com/workitem/33224">http://shfb.codeplex.com/workitem/33224</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
<ul><li>Add a transformation to match the SHFB hashed member naming option method. That would get rid of the need to load the reflection file in SHFB after applying the doc model transformation. <a href="http://shfb.codeplex.com/workitem/33233">http://shfb.codeplex.com/workitem/33233</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffSun, 23 Dec 2012 20:11:45 GMTUpdated Wiki: Future Enhancements and Features 20121223081145PUpdated Wiki: Documentationhttp://shfb.codeplex.com/documentation?version=10<div class="wikidoc"><h2>Installation and Usage</h2>
Download the <a href="http://shfb.codeplex.com/releases">latest release</a>, extract it to a folder, and then run <b>SandcastleInstaller.exe</b> to run the guided installation of Sandcastle, the various extra items from the Sandcastle Styles project, and the Sandcastle Help File Builder.<br /><br />See the <a href="http://www.ewoodruff.us/shfbdocs/Index.aspx?topic=html/8c0c97d0-c968-4c15-9fe9-e8f3a443c50a.htm">Installation Instructions</a> topic for more information about the required set of additional tools.<br /><br />If you are new to Sandcastle and the help file builder, see the topics in the <a href="http://www.ewoodruff.us/shfbdocs/Index.aspx?topic=html/b772e00e-1705-4062-adb6-774826ce6700.htm">Getting Started</a> section to get familiar with it, set up your projects to produce XML comments, and create a help file project. A full copy of the help file is also included with the installer and a shortcut to it can be found in the <i>Sandcastle Help File Builder</i> folder in the <i>Start | All Programs</i> menu.<br />
<h2>Viewing Downloaded Help Files</h2>
The help files contained in the project downloads may need to be unblocked before you can view their content. If you do not see any information in the content pane after opening a help file, do the following:<br />
<ul><li>Copy the help file to your hard drive and open it from there. Trying to view a help file from a network share can cause the content to be blocked.</li>
<li>If a security dialog appears asking if you want to open the file, uncheck the &quot;Always ask before opening this file&quot; checkbox.</li>
<li>If the file is still blocked, open Windows Explorer, right-click the CHM file, select <b>Properties</b>, and then click the <b>Unblock</b> option.</li>
<li>Apply the file property changes and open the help file again.</li></ul>
<h2>Online Help and Guides</h2>
<ul><li><a href="http://www.ewoodruff.us/shfbdocs">Sandcastle Help File Builder</a></li>
<li><a href="http://www.ewoodruff.us/sandcastletools">Sandcatle Tools</a></li>
<li><a href="http://www.ewoodruff.us/mamlguide">Sandcastle MAML Guide</a></li>
<li><a href="http://www.ewoodruff.us/xmlcommentsguide">Sandcastle XML Comments Guide</a></li></ul>
<h2>Future Enhancements</h2>
For a list of planned future enhancements and features, see the <a href="http://shfb.codeplex.com/wikipage?title=Future%20Enhancements%20and%20Features&referringTitle=Documentation">Future Enhancements and Features</a> page.<br />
<h2>Other Resources</h2>
<a href="http://www.ewoodruff.us/shfbdocs/?topic=html/bd1ddb51-1c4f-434f-bb1a-ce2135d3a909.htm">Sandcastle Help File Builder - Benefits and Features</a><br /><a href="http://www.ewoodruff.us/shfbdocs/Index.aspx?topic=html/8e3f8757-0ef3-4772-bb2f-5d7ae57e50da.htm">Sandcastle Help File Builder Overview</a><br /><a href="http://www.ewoodruff.us/shfbdocs/Index.aspx?topic=html/b128ad2a-787e-48c7-b946-f6953080c386.htm">Visual Studio Integration Package</a><br /><a href="http://www.ewoodruff.us/shfbdocs/Index.aspx?topic=html/c18d6cb6-e4e4-4944-84ee-f867aa6cfb0d.htm">Links to Resources</a><br /><a href="http://www.ewoodruff.us/shfbdocs/Index.aspx?topic=html/078cc1c7-7995-431e-bf9c-8813becbe8df.htm">Version History</a><br /><a href="http://www.ewoodruff.us/SHFBDonate.html">Make a Donation to Support the Project</a><br /></div><div class="ClearBoth"></div>EWoodruffSun, 16 Dec 2012 21:59:45 GMTUpdated Wiki: Documentation 20121216095945PUpdated Wiki: Future Enhancements and Featureshttp://shfb.codeplex.com/wikipage?title=Future Enhancements and Features&version=7<div class="wikidoc">Below is a list of future enhancements and features for the Sandcastle tools and the Sandcastle Help File Builder. No planned release dates have been set for these items. Each item may be implemented all at once or a little at a time depending on its scope and complexity. If you&#39;d like to comment on any of these, please do so on the related work item page (see the links below) or, to make additional suggestions, please <a href="http://shfb.codeplex.com/discussions">start a new discussion</a>.<br />
<h2>Sandcastle Tools</h2>
<ul><li>See if there is a way to improve the keyword index in Help 1 and Website output so that member names common to multiple classes are differentiated in the index. <a href="http://shfb.codeplex.com/workitem/32262">http://shfb.codeplex.com/workitem/32262</a></li></ul>
<ul><li>Expose as public many of the internal BuildAssembler-related classes used for stuff like target info. That will make it easier to reuse the classes in third-party components and third-party components derived from existing Sandcastle build components. <a href="http://shfb.codeplex.com/workitem/33223">http://shfb.codeplex.com/workitem/33223</a></li></ul>
<ul><li>Investigate improving the performance of BuildAssembler. Things to consider:
<ul><li>Sharing information between build components that use the same info rather than loading it again.</li>
<li>Use pre-built cache files to save on initialization time.</li>
<li>Use pre-built cache files to load information on demand to reduce memory usage.</li>
<li>Longer term, investigate the possibility of having BuildAssembler build topics in parallel. That would require that all build components in the stack are thread safe though.</li>
<li><a href="http://shfb.codeplex.com/workitem/33224">http://shfb.codeplex.com/workitem/33224</a></li></ul></li></ul>
<ul><li>Remove the remaining branding stuff from the VS2010 style and SHFB. Branding support seemed like a good idea but with the changes in HV2, that is not the case and it has proven to be more trouble than it was worth. Sandcastle output requires some level of self-branding as non-self-branded content would not be able to use any custom scripts and stylesheets used for things like code colorization or other such features added by custom build components that rely on them. Supporting alternate branding packages doesn&#39;t seem to make sense as that&#39;s what presentation styles are for. In short, it makes better sense to treat all Sandcastle presentation styles as self-branded and remove the use of branding packages. <a href="http://shfb.codeplex.com/workitem/33225">http://shfb.codeplex.com/workitem/33225</a></li></ul>
<ul><li>Investigate whether or not a folder name can safely be introduced into the GUID and hashed member name naming methods to reduce the number of files in the root HTML output folder. <a href="http://shfb.codeplex.com/workitem/33058">http://shfb.codeplex.com/workitem/33058</a></li></ul>
<ul><li>Create an Open XML presentation style with any related build components that outputs the help as an Open XML document. The resulting output document should be readily convertible to other formats such as PDF without having to add additional presentation styles or conversion tools to Sandcastle. <a href="http://shfb.codeplex.com/workitem/33226">http://shfb.codeplex.com/workitem/33226</a></li></ul>
<ul><li>Create an MSDN Lightweight presentation style for website output that mimics the current MSDN website pages with the TOC info in each page. <a href="http://shfb.codeplex.com/workitem/33227">http://shfb.codeplex.com/workitem/33227</a></li></ul>
<ul><li>Perhaps update the tools to enable them to run as MSBuild tasks. Also, there are a lot of obsolete files that should be removed (i.e. Microsoft-specific configuration files that serve no apparent useful purpose). If possible, update the Sandcastle tools and build scripts to utilize a modified version of the presentation style definition file. <a href="http://shfb.codeplex.com/workitem/33373">http://shfb.codeplex.com/workitem/33373</a></li></ul>
<ul><li>As time permits, add more information to the Sandcastle tools help file that describes the various tools and how they work. <a href="http://shfb.codeplex.com/workitem/33228">http://shfb.codeplex.com/workitem/33228</a></li></ul>
<h2>Sandcastle Help File Builder</h2>
<ul><li>Update MRefBuilder to support the Visibility options from SHFB directly. This would be more efficient as the unwanted members could be stripped during the reflection phase rather than after the fact which requires loading the reflection data XML file. <a href="http://shfb.codeplex.com/workitem/33231">http://shfb.codeplex.com/workitem/33231</a></li></ul>
<ul><li>Move some of the SHFB build components that aren&#39;t tied to SHFB such as the IntelliSenseComponent, ShowMissingComponent, etc. into Sandcastle along with any related resource items (i.e. Show Missing messages). <a href="http://shfb.codeplex.com/workitem/33232">http://shfb.codeplex.com/workitem/33232</a></li></ul>
<ul><li>Add a transformation to match the SHFB hashed member naming option method. That would get rid of the need to load the reflection file in SHFB after applying the doc model transformation. <a href="http://shfb.codeplex.com/workitem/33233">http://shfb.codeplex.com/workitem/33233</a></li></ul>
</div><div class="ClearBoth"></div>EWoodruffSun, 16 Dec 2012 21:30:22 GMTUpdated Wiki: Future Enhancements and Features 20121216093022P