如何在从外部 URL 加载内容的 .NET 应用程序中提供上下文相关帮助？
我们有一个基于 Plone 的 Intranet，其中填充了 .NET 应用程序的文档，但目前 .NET 应用程序中的上下文相关 (F1) 帮助与 Plone 内容之间没有任何连接。
我们不想创建和“推送”分发 CHM 并维护两个不同的文档存储库，而是希望将所有文档保留在 Plone 中，其中内容可以随时“拉取”并且始终会存在是最新的并有全文索引。
我们希望能够允许用户按 F1 并以某种方式自动加载与该主题相关的 URL，其中可能包含一个锚点 (http://intranet/general-topic#subtopic)直接跳转到相应的内容。
在 .NET 应用程序中显示帮助内容（也许在其“帮助”窗口中）是理想的选择，但如果需要实例化浏览器，那也可能没问题。
理想情况下，我们希望将应用程序中的上下文元素链接到 URL 的任务由正在开发文档的业务分析师执行，而不是开发人员。
这可能吗？如果是这样，我们将如何在应用程序的每个上下文与其 F1 帮助应显示的 URL 之间创建“映射”？
We have a Plone-based intranet populated with documentation for our .NET app, but currently there is no connection between the context-sensitive (F1) help in the .NET app and the Plone content.
Rather than having to create and "push"-distribute (a) CHM(s) and maintain two distinct repositories of documentation, we'd like to keep all the docs within Plone where content can be "pulled" at any time and will always be up-to-date and full-text indexed.
We'd like to be able to allow users to hit F1 and somehow automatically load a URL related to that topic, which could include an anchor (http://intranet/general-topic#subtopic) to jump straight to the appropriate content.
Showing the help content within the .NET app -- maybe within its "Help" window -- would be ideal, but if it needs to instantiate a browser, that might be fine, too.
Ideally we'd like the task of linking context elements in the application to URLs to be performed by the business analysts that are developing the documentation, not developers.
Is this possible? If so, how would we go about creating the "mappings" between each context of the app and the URL its F1 help should display?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
假设您的应用程序有某种数据库后端，我将创建一个表来映射控件/表单（取决于您想要的上下文敏感程度）及其相应的帮助网址。
从那里看来，将该 URL 加载到 Web 浏览器控件中或分离一个新的浏览器窗口似乎很简单。
assuming your application has some sort of database backend, i would create a table to map between control/forms (depending on how context sensitive you want to be) and their corresponding help urls.
from there it seems like it would be simple enough to either load that url into webbrowser control or spin off a new browser window.