pdxwordsmith wrote:I upgraded to Flare 5 and my online help (WebHelp for Silverlight app) stopped working. It appears that there is a new file, index.mcwebhelp in the webhelp output that Microsoft doesn't like.
From my engineer:
We have a problem with the deployment of the online help. While looking at the problem, I am noticing that the Microsoft Setup functionality doesn’t want to include the index.mcwebhelp file, because it doesn’t have an extension that it thinks should be on a file that it should include. Since that file actually is an xml file, I was wondering why it can’t have an .xml extension on it. But I have no idea where these files come from.
Of course I should figure out how to make Microsoft include this file, or Microsoft should include these files, but if the extension is arbitrary, maybe we could fix it by adding the .xml suffix to the file name.
I searched the Flare OLH for mention of this file - thinking maybe I could change the extension in my project, but no topics found. Has anyone else encountered this issue and/or can you shed light on the purpose of this file?
Thanks,
Hi, PDX.
Yes; search on "Merging Output in Flare WebHelp Projects" in Help. We recently appended both of our service Web sites with an online 2010 Parts Catalog, developed separately as a stand-alone project. The 'child' project is first built into its output, and before building the 'parent' site, we have a link set up in its master TOC. Highlight and press F4 to open the properties dialog. This has the Link field, to hook up with the child output, for sucking the child output into the build of the parent (sounds a little dangerous, I know:-). You do this by selecting "../../ChildProjectName/Output/MyWebHelp/
index.mcwebhelp".
Anyway, that's basically our familiarity with this particular file. This seems typical of the somewhat hubristic Microsoft; if you ever need to merge WebHelp outputs, then the MS setup needs to be a little more accommodating. Hope this helps you some,
cheers, =dg=