<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>SHFB Forum Rss Feed</title><link>http://www.codeplex.com/Project/ListForums.aspx?ProjectName=SHFB</link><description>SHFB Forum Rss Description</description><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;I certainly did, the &lt;strong&gt;CopyToMedia&lt;/strong&gt; is something else, I check it later. Now this is the way to do;-)&lt;br /&gt;
&lt;h1&gt;Use images, not referenced by &lt;em&gt;MAML&lt;/em&gt; topics&lt;/h1&gt;
Import the [images]-folder into shfb &lt;em&gt;Project Explorer&lt;/em&gt;, not referenced by &lt;em&gt;MAML&lt;/em&gt; topics:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Select &lt;em&gt;Add&lt;/em&gt;  and &lt;em&gt;Existing Folder...&lt;/em&gt; from tree context menu, select the [images]-folder&lt;/li&gt;
&lt;li&gt;For each image-file, set &lt;strong&gt;BuildAction&lt;/strong&gt; from &lt;em&gt;Image&lt;/em&gt; to &lt;em&gt;Content&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;
In shfb, push the &lt;em&gt;Build the help file&lt;/em&gt; button&lt;br /&gt;
&lt;/li&gt;
&lt;/ol&gt;
After the build, you have a &amp;lt;appname&amp;gt;.chm help file, with images. Easy :-).&lt;br /&gt;
&lt;br /&gt;
Regards&lt;br /&gt;
/Jonas&lt;br /&gt;
&lt;/div&gt;</description><author>Guson</author><pubDate>Tue, 21 May 2013 06:18:13 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130521061813A</guid></item><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;I think you missed what I said in my first response.  If these the images are not being used in MAML topics, just set the BuildAction in the SHFB project to &lt;strong&gt;Content&lt;/strong&gt; and place them in an &lt;strong&gt;Images&lt;/strong&gt; folder off the root of the project.  They'll get copied into the working folder automatically and compiled into the help file.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Mon, 20 May 2013 16:33:45 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130520043345P</guid></item><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;&lt;h1&gt;Batch for all help file formats&lt;/h1&gt;
&lt;pre&gt;&lt;code&gt;@ECHO OFF
:: 1. In shfb, push the &amp;quot;Build the help file&amp;quot; button
:: 2. In &amp;quot;Build Output&amp;quot; wait for the &amp;quot;Clearing working folder...&amp;quot; output
:: 3. Run this batch file

REM Comment/uncomment in Build selected help file formats
REM HTML Help1 (CHM)
xcopy images\*.* help\Working\Output\HtmlHelp1\images\*.* /q /y
REM MS Help 2 (HxS)
REM xcopy images\*.* help\Working\Output\MSHelp2\images\*.* /q /y
REM MS Help Viewer (MSHC)
REM xcopy images\*.* help\Working\Output\MSHelpViewer\images\*.* /q /y
REM Website (HTML/ASP.NET)
REM xcopy images\*.* help\Working\Output\Website\images\*.* /q /y&lt;/code&gt;&lt;/pre&gt;

I havent verifyed &lt;em&gt;MS help 2&lt;/em&gt; and &lt;em&gt;MS Help Viewer&lt;/em&gt;.&lt;br /&gt;
&lt;/div&gt;</description><author>Guson</author><pubDate>Mon, 20 May 2013 12:06:51 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130520120651P</guid></item><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;Yes! I did'it, with &lt;em&gt;MS help1&lt;/em&gt; file. ;-)&lt;br /&gt;
I did a longshot, when building the help file.&lt;br /&gt;
&lt;h1&gt;Create a batch containing:&lt;/h1&gt;
&lt;pre&gt;&lt;code&gt;@ECHO OFF
xcopy images\*.* help\Working\Output\HtmlHelp1\images\*.* /q /y&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;Build help file&lt;/h1&gt;
&lt;ol&gt;
&lt;li&gt;In shfb, push the &lt;em&gt;Build the help file&lt;/em&gt; button&lt;/li&gt;
&lt;li&gt;In &lt;em&gt;Build Output&lt;/em&gt; wait for the &lt;em&gt;Clearing working folder...&lt;/em&gt; output&lt;/li&gt;
&lt;li&gt;
Run the batch file&lt;br /&gt;
&lt;/li&gt;
&lt;/ol&gt;
After the build, you have a &amp;lt;appname&amp;gt;.chm help file, with images. Not so easy, but the result was correct.&lt;br /&gt;
&lt;/div&gt;</description><author>Guson</author><pubDate>Mon, 20 May 2013 10:54:50 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130520105450A</guid></item><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;Hi!&lt;br /&gt;
The help file is currently only for internal usage, so I prefere &lt;em&gt;MS Help1&lt;/em&gt; file (one file, easy to use).&lt;br /&gt;
&lt;h1&gt;New file structure&lt;/h1&gt;
I changed my file structure, if I want to produce other help-formats. I imported the [images]-folder into shfb &lt;em&gt;Project Explorer&lt;/em&gt;, and marked the images as &lt;strong&gt;CopyToMedia=True&lt;/strong&gt;. I use &lt;em&gt;.NET Framework 4.5&lt;/em&gt; in &lt;strong&gt;Build&lt;/strong&gt; settings.&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;[appname]\
    [doc]\
        [help] (shfb-output, temprary folder)
        [images]\ (images-folder, to use in shfb-build)
        &amp;lt;appname&amp;gt;.shfbproj
        &amp;lt;appname&amp;gt;.chm (copied from [help]-folder)
    [projname]\ (the VS project)
    &amp;lt;appname&amp;gt;.sln&lt;/code&gt;&lt;/pre&gt;

And the [help]-folder (shfb-output) is only used as a temprary folder.&lt;br /&gt;
&lt;h1&gt;Source code documentation&lt;/h1&gt;
The path is relative to the [help] (shfb-output) folder, i guess after your description.&lt;br /&gt;
The images is referenced from XML documentation in source code, like this:&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;&amp;lt;img src=&amp;quot;..\images\ControlBox.png&amp;quot; alt=&amp;quot;ControlBox Class Diagram&amp;quot; /&amp;gt;&lt;/code&gt;&lt;/pre&gt;

&lt;h1&gt;SHBF builds&lt;/h1&gt;
I have tryed all build formats, and the only one that I can get to work is &lt;em&gt;Website (HTML/ASP.NET)&lt;/em&gt;, if I manually copy the [images]-folder into the [help]-folder, after a shfb-build. And its okey with a html help. I could do a batch, containing:&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;@ECHO OFF
xcopy images\*.* help\images\*.* /q /y
%SystemRoot%\Microsoft.NET\Framework\v4.0.30319\msbuild.exe &amp;lt;appname&amp;gt;.shfbproj
pause
help\Index.html&lt;/code&gt;&lt;/pre&gt;

And in shfb proj change to include the [projname]&amp;lt;projname&amp;gt;.csproj insted of &amp;lt;appname&amp;gt;.sln, because I get some error running the batch, no problen running in shbf gui. (SHFB : error BE0042: You must specify at least one documentation source)&lt;br /&gt;
&lt;h1&gt;MAML-pages&lt;/h1&gt;
I have not tryed adding/using MAML-pages, but it maybe a better aproach, then I could extend code documentation, with custom Welcome-, History-, Class description-pages, before the code documentation.&lt;br /&gt;
&lt;/div&gt;</description><author>Guson</author><pubDate>Mon, 20 May 2013 10:11:23 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130520101123A</guid></item><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;The basePath only relates to the code block component which has no bearing on how images are displayed or referenced.  In relation to imported code blocks, the base path is the project folder.&lt;br /&gt;
&lt;br /&gt;
Bear in mind that when you add an image to a SHFB project, it's default BuildAction is set to Image with the assumption that it will be used in MAML topics.  With that build action, it only gets copied if referenced in a MAML topic and will end up in the Media\ folder.  Setting the CopyToMedia property to true will force it to always get copied to the .\Media folder even if not referenced in MAML topics.&lt;br /&gt;
&lt;br /&gt;
If your intent is to simply use it from XML comments, set its BuildAction property to Content so that it is always copied to the output folder.  If located at the root, it will get copied to the root of the help content.  If in a subfolder, it will get copied to a like-named subfolder in the help content.  From there, the information in the FAQ entry is correct.  Use either a relative path (..\Image.png) or relative path with subfolder (..\Images\Image.png) to access it.&lt;br /&gt;
&lt;br /&gt;
However, if producing MS Help Viewer output, the above may not work as I recall since the viewer modifies the URLs.  I'd have to try it and see if there's a way to make it work.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Fri, 17 May 2013 19:32:30 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130517073230P</guid></item><item><title>New Post: Add images in XML doc</title><link>http://shfb.codeplex.com/discussions/444057</link><description>&lt;div style="line-height: normal;"&gt;Hi!&lt;br /&gt;
I have used &lt;a href="https://shfb.codeplex.com/" rel="nofollow"&gt;SHFB&lt;/a&gt;, to produce code documentation for a while, and now I want to add pictures like class diagram and so on.&lt;br /&gt;
&lt;h1&gt;SHFB - Project Properties&lt;/h1&gt;
In SHFB project settings I have:&lt;br /&gt;
[Paths/Output Paths/Help content output path] = doc\&lt;br /&gt;
(Warning: The output folder will be erased, when building a web-site)&lt;br /&gt;
&lt;h1&gt;My file structure&lt;/h1&gt;
&lt;pre&gt;&lt;code&gt;[appname]\
    [doc]\ (shfb-output)
    [img]\ (images)
    [projname]\ (the VS project)
    &amp;lt;appname&amp;gt;.shfbproj
    &amp;lt;appname&amp;gt;.sln&lt;/code&gt;&lt;/pre&gt;

&lt;strong&gt;Description&lt;/strong&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;[] - folder&lt;/li&gt;
&lt;li&gt;&amp;lt;&amp;gt; - file&lt;/li&gt;
&lt;li&gt;
() - comment&lt;br /&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Questions&lt;/h1&gt;
(From SHBF documentation) &amp;quot;The path is relative to the basePath configuration element.&amp;quot;&lt;br /&gt;
&lt;strong&gt;Q: What is the &amp;quot;basePath&amp;quot;?&lt;/strong&gt;&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;doc&lt;/li&gt;
&lt;li&gt;doc\Working\Output\HtmlHelp1&lt;/li&gt;
&lt;li&gt;
projname&lt;br /&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;strong&gt;I cant get it to work, only placeholder of image.&lt;/strong&gt;&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;&amp;lt;img src=&amp;quot;ControlBox.png&amp;quot; alt=&amp;quot;ControlBox Class Diagram&amp;quot; /&amp;gt;&lt;/li&gt;
&lt;li&gt;&amp;lt;img src=&amp;quot;../ControlBox.png&amp;quot; alt=&amp;quot;ControlBox Class Diagram&amp;quot; /&amp;gt;&lt;/li&gt;
&lt;li&gt;
&amp;lt;img src=&amp;quot;../img/ControlBox.png&amp;quot; alt=&amp;quot;ControlBox Class Diagram&amp;quot; /&amp;gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;strong&gt;Q: How to add image-path(s) to shfbproj-file&lt;/strong&gt;&lt;br /&gt;
Why: &lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;I would prefere to specify (a list of) image-folder(s), when runing the shfb project&lt;/li&gt;
&lt;li&gt;
In XML doc of code-file only use file name, &amp;lt;img src=&amp;quot;ControlBox.png&amp;quot; alt=&amp;quot;ControlBox Class Diagram&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;strong&gt;Q: List of supported image formats&lt;/strong&gt;&lt;br /&gt;
?: (gif, jpg, png)&lt;br /&gt;
&lt;h1&gt;Links&lt;/h1&gt;
&lt;strong&gt;SHBF - Discussions&lt;/strong&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://shfb.codeplex.com/discussions/360087" rel="nofollow"&gt;Sandcastle help builder - Dead pictures&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://shfb.codeplex.com/discussions/223167" rel="nofollow"&gt;Post-Transform Components for Logo: How to make relative Path &lt;/a&gt;&lt;br /&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;strong&gt;SHFB - FAQ&lt;/strong&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.ewoodruff.us/shfbdocs/html/1aea789d-b226-4b39-b534-4c97c256fac8.htm#EmbedImage" rel="nofollow"&gt;How can I embed an image in a namespace, type, or member help topic?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.ewoodruff.us/shfbdocs/html/7f03ba39-09f8-4320-bdbd-ed31a3bd885f.htm" rel="nofollow"&gt;Code Block Component&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>Guson</author><pubDate>Fri, 17 May 2013 14:02:10 GMT</pubDate><guid isPermaLink="false">New Post: Add images in XML doc 20130517020210P</guid></item><item><title>New Post: Caching to speed up FillNode.aspx</title><link>http://shfb.codeplex.com/discussions/443303</link><description>&lt;div style="line-height: normal;"&gt;I'll have to ask whether my employer is willing to contribute the changes.&lt;br /&gt;
If not, someone else can perhaps implement a similar solution.&lt;br /&gt;
&lt;/div&gt;</description><author>Takajalka</author><pubDate>Tue, 14 May 2013 23:01:46 GMT</pubDate><guid isPermaLink="false">New Post: Caching to speed up FillNode.aspx 20130514110146P</guid></item><item><title>New Post: Markdown Support</title><link>http://shfb.codeplex.com/discussions/443507</link><description>&lt;div style="line-height: normal;"&gt;Nobody has as far as I know.  The main task would be creating a presentation style that generated the output in markdown format.  Depending on how far you wanted to take it, some work may also need to be done on a few of the build components since they all assume HTML output.  For example, the reference link components would need to be updated to support outputting the links in the markdown format rather than as HTML anchor links.  If generating API topics, the syntax generators use CSS styles to colorize the code in the syntax sections so they may need to change as well.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Mon, 13 May 2013 19:33:33 GMT</pubDate><guid isPermaLink="false">New Post: Markdown Support 20130513073333P</guid></item><item><title>New Post: Caching to speed up FillNode.aspx</title><link>http://shfb.codeplex.com/discussions/443303</link><description>&lt;div style="line-height: normal;"&gt;If you'd care to share your changes, I'd be happy to merge them into a future release of SHFB.  You can open a work item here and attach them to it or e-mail me the changes.  My e-mail address is in the About box in the standalone GUI and in the footer of the pages in the help file.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Mon, 13 May 2013 19:17:56 GMT</pubDate><guid isPermaLink="false">New Post: Caching to speed up FillNode.aspx 20130513071756P</guid></item><item><title>New Post: BUILDASSEMBLER : error : The target attribute is missing or has no value</title><link>http://shfb.codeplex.com/discussions/442383</link><description>&lt;div style="line-height: normal;"&gt;The error has been converted back to a warning for the next release with a better message that gives a hint as to the cause of the problem.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Mon, 13 May 2013 19:12:10 GMT</pubDate><guid isPermaLink="false">New Post: BUILDASSEMBLER : error : The target attribute is missing or has no value 20130513071210P</guid></item><item><title>New Post: Markdown Support</title><link>http://shfb.codeplex.com/discussions/443507</link><description>&lt;div style="line-height: normal;"&gt;Has anybody modified Sandcastle to produce markdown, rather than HTML, output?&lt;br /&gt;
&lt;/div&gt;</description><author>ssmith</author><pubDate>Mon, 13 May 2013 17:27:25 GMT</pubDate><guid isPermaLink="false">New Post: Markdown Support 20130513052725P</guid></item><item><title>New Post: Caching to speed up FillNode.aspx</title><link>http://shfb.codeplex.com/discussions/443303</link><description>&lt;div style="line-height: normal;"&gt;A better solution:&lt;br /&gt;
&lt;br /&gt;
Define classes for the HelpTOC and HelpTOCNode elements, and load WebTOC.xml to them with XmlSerializer.  Take all the nodes that have IDs, and collect them to a Dictionary&amp;lt;Guid, TocNode&amp;gt; instance.  Insert this dictionary into Page.Cache, with the appropriate CacheDependency.  On each request, find the correct node from the dictionary, and show its children.  Because Dictionary&amp;lt;TKey, TValue&amp;gt; is thread-safe for multiple readers, no locking is needed after initialization.&lt;br /&gt;
&lt;br /&gt;
After the application pool has been restarted, the first use of FillNode.aspx takes about 880 ms in this solution.  That includes the time XmlSerializer spends generating and compiling the serialization assembly.  Subsequent requests typically take only two milliseconds, so the IIS output cache is no longer useful.  If the WebTOC.xml file is modified, then FillNode.aspx automatically reloads it with the previously generated serialization assembly; this takes about 430 ms.&lt;br /&gt;
&lt;br /&gt;
The initialization time could be improved by replacing XmlSerializer with hardcoded methods that use XmlReader, but 880 ms is already fast enough for something that runs perhaps once a day, and custom deserialization would make later maintenance more expensive.&lt;br /&gt;
&lt;/div&gt;</description><author>Takajalka</author><pubDate>Mon, 13 May 2013 16:02:27 GMT</pubDate><guid isPermaLink="false">New Post: Caching to speed up FillNode.aspx 20130513040227P</guid></item><item><title>New Post: BUILDASSEMBLER : error : The target attribute is missing or has no value</title><link>http://shfb.codeplex.com/discussions/442383</link><description>&lt;div style="line-height: normal;"&gt;My problem was that I had used 'member' instead of 'cref' as the attribute name.&lt;br /&gt;
Without this thread I would never have found the cause of the problem.&lt;br /&gt;
&lt;br /&gt;
A more helpful error message, and the option to make it just a warning, would be much appreciated.&lt;br /&gt;
&lt;/div&gt;</description><author>rp</author><pubDate>Mon, 13 May 2013 13:38:54 GMT</pubDate><guid isPermaLink="false">New Post: BUILDASSEMBLER : error : The target attribute is missing or has no value 20130513013854P</guid></item><item><title>New Post: Caching to speed up FillNode.aspx</title><link>http://shfb.codeplex.com/discussions/443303</link><description>&lt;div style="line-height: normal;"&gt;With a 12-megabyte WebTOC.xml, the single-user response times from FillNode.aspx are typically between 500 and 600 milliseconds, as shown by the Web Console in the Firefox browser.  This is because FillNode.aspx parses the entire file to a new XPathDocument instance on each request.&lt;br /&gt;
&lt;br /&gt;
If I change FillNode.aspx to cache the XPathDocument instance between requests, then the single-user response time is only around 120 milliseconds; typically between 115 and 125.  This is with a CacheDependency on the file and lock (toc) { ... } around everything that accesses the XML nodes after they have been read from the cache.  (Although XPathDocument is read-only on the surface, it is not thread-safe.)  Such serialization may be bad for scaling to hundreds of simultaneous users but I suspect the current code wouldn't work too well in that situation either.  For better parallelism, one might consider setting up a pool of XPathDocument instances, or using the thread ID or processor ID as part of the cache key.&lt;br /&gt;
&lt;br /&gt;
Far better savings can be achieved by configuring IIS user-mode output caching to consider only the &amp;quot;Id&amp;quot; and &amp;quot;topic&amp;quot; query string variables and ignore the &amp;quot;hash&amp;quot; variable.  If the data is already in the cache, then the response time is typically only 1 or 2 milliseconds.  However, each cache entry only covers one parent node, and the output cache tends to discard rarely-used entries pretty soon after the last use.  Thus, for the best performance, the IIS output cache should be used together with XPathDocument caching.&lt;br /&gt;
&lt;/div&gt;</description><author>Takajalka</author><pubDate>Fri, 10 May 2013 21:43:25 GMT</pubDate><guid isPermaLink="false">New Post: Caching to speed up FillNode.aspx 20130510094325P</guid></item><item><title>New Post: Code in &lt;code&gt; blocks not keeping indentation spacing</title><link>http://shfb.codeplex.com/discussions/443279</link><description>&lt;div style="line-height: normal;"&gt;Thank you so much for your quick response!&lt;br /&gt;
&lt;br /&gt;
I have discovered that this is an issue because I am using WCFExtras+ to pull the comments into a generated service contract, and that tool is eliminating all my formatting.  I apologize for wasting your time with my question.&lt;br /&gt;
&lt;br /&gt;
Thanks again!&lt;br /&gt;
&lt;/div&gt;</description><author>JHolland</author><pubDate>Fri, 10 May 2013 20:02:11 GMT</pubDate><guid isPermaLink="false">New Post: Code in &lt;code&gt; blocks not keeping indentation spacing 20130510080211P</guid></item><item><title>New Post: Token within Token?</title><link>http://shfb.codeplex.com/discussions/441282</link><description>&lt;div style="line-height: normal;"&gt;I finally got around to checking this and nested tokens are working as expected.  Typically, if a token is not found, you'll get no output at all, not just the token name.  You didn't say whether this was in a MAML topic or in XML comments.  If in XML comments, you do need to add the API Token Resolution build component to the project in order for the tokens to get replaced.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Fri, 10 May 2013 19:31:47 GMT</pubDate><guid isPermaLink="false">New Post: Token within Token? 20130510073147P</guid></item><item><title>New Post: Code in &lt;code&gt; blocks not keeping indentation spacing</title><link>http://shfb.codeplex.com/discussions/443279</link><description>&lt;div style="line-height: normal;"&gt;As long as it's nested within an example element, it should render just fine.  If you've got the Indent HTML project option enabled, turn it off as it will cause problems with the format, though it usually only affects the first line.  That option is for debugging the output and should be typically left disabled.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Fri, 10 May 2013 19:24:46 GMT</pubDate><guid isPermaLink="false">New Post: Code in &lt;code&gt; blocks not keeping indentation spacing 20130510072446P</guid></item><item><title>New Post: Code in &lt;code&gt; blocks not keeping indentation spacing</title><link>http://shfb.codeplex.com/discussions/443279</link><description>&lt;div style="line-height: normal;"&gt;I have tried several different variations in my code block to try to get the output help documentation to have formatted C# code, but they all end up with the entire code block left aligned.  Is there a way to get the spacing to persist to the generated help file?&lt;br /&gt;
&lt;br /&gt;
e.g.&lt;br /&gt;
&lt;pre&gt;&lt;code&gt;/// &amp;lt;code lang=&amp;quot;C#&amp;quot;&amp;gt;
/// using MyClass.ServiceContracts;
/// class Program
/// {
///     static void Main(string[] args)
///     {
///         MyClient _myClient = new MyClient();
///         MyRequest _myRequest = new MyRequest();
///         _myClient.performRequest(_myRequest);
///     }
/// }
/// &amp;lt;/code&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

comes out as:&lt;br /&gt;
&lt;br /&gt;
using MyClass.ServiceContracts;&lt;br /&gt;
class Program&lt;br /&gt;
{&lt;br /&gt;
static void Main(string[] args)&lt;br /&gt;
{&lt;br /&gt;
MyClient _myClient = new MyClient();&lt;br /&gt;
MyRequest _myRequest = new MyRequest();&lt;br /&gt;
_myClient.performRequest(_myRequest);&lt;br /&gt;
}&lt;br /&gt;
}&lt;br /&gt;
&lt;/div&gt;</description><author>JHolland</author><pubDate>Fri, 10 May 2013 18:40:34 GMT</pubDate><guid isPermaLink="false">New Post: Code in &lt;code&gt; blocks not keeping indentation spacing 20130510064034P</guid></item><item><title>New Post: Website ouput: Merge documentation from different sources</title><link>http://shfb.codeplex.com/discussions/442399</link><description>&lt;div style="line-height: normal;"&gt;A build component is probably not necessary. Reference links are generated by ResolveReferenceLinksComponent2 and ResolveConceptualLinksComponent.  By default, they contain no path, just the GUID plus a &amp;quot;.htm&amp;quot; extension.  ResolveReferenceLinksComponent2 supports an href-format attribute that defines the local link format.  ResolveConceptualLinksComponent supports a url attribute on the target elements that defines the link format.&lt;br /&gt;
&lt;br /&gt;
SHFB does not use nor does it expose a way to alter those attributes.  In order to change them, you could write a plug-in that alters the configuration files to add the appropriate attributes to the necessary configuration elements.  I haven't looked to closely at the required format nor have I documented them yet so you'd have to poke around in the build component source code to figure out the required value format.  There's a topic in the SHFB help file on writing plug-ins so that would be the place to look for into on writing the actual plug-in.&lt;br /&gt;
&lt;br /&gt;
Eric&lt;br /&gt;
&lt;/div&gt;</description><author>EWoodruff</author><pubDate>Wed, 08 May 2013 19:29:55 GMT</pubDate><guid isPermaLink="false">New Post: Website ouput: Merge documentation from different sources 20130508072955P</guid></item></channel></rss>