“自述”的最佳位置是什么？使用 .MSI 包部署 ASP.NET 应用程序时目标计算机上的 .MSI 文件？
对于打包并出售给客户进行部署的 ASP.NET Web 应用程序，包含有关目标系统上的设置和配置说明的“自述文件”的最佳位置是什么？
要求：
- 该文件不应被 仅网络应用程序的用户 进行设置的人以及 配置。
- 该文件应该是 由 MSI 安装程序消耗 程序，以便可以显示 作为设置向导 UI 的一部分。
- 解决方案应该很简单而且非常 低成本。 （我不想详细说明 仅简单文本的解决方案 我的一些想法是将文件
复制到 *App_Data* 或 bin，因为默认情况下这些文件夹是受保护的文件夹，然后从安装程序中的这些位置之一提取文件。
For an ASP.NET web application that is packaged and sold to customers for deployment, what would be the best location for a "read me" file with notes about setup and configuration on the target system?
Requirements:
- The file should not be accessible by
users of the web application, only
the person doing setup and
configuration. - The file should be
consumable by the MSI installer
program, so that it can be displayed
as part of the setup wizard UI. - The solution should be simple and very
low cost. (I don't want an elaborate
solution for just a simple text
file.)
Some thoughts I have are to copy the file to *App_Data* or to bin as those are protected folders by default, and then pull the file in from one of those locations in the setup program.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
自述文件应该是一个单独的文件，位于您分发 Web 应用程序的媒体上的 MSI 旁边。这是
几代人之前黑暗时代的标准做法。如果您从网络下载分发，则有一个 MSI 链接和一个自述文件链接。您还可以将相同的文件包含到 MSI 中，但可以说这是错误的位置，因为用户尚未到达配置阶段，除非他们打印它，否则稍后将无法在 MSI 中引用它过程（如果 MSI 中有任何配置步骤）。
通过 Web 应用程序提供说明也可以说是错误的，因为用户可能必须进行一些初始配置才能到达告诉他们如何配置应用程序的页面......
因此，将说明单独发送给 MSI，并且确保它们打印出来后看起来不错并且易于阅读。请记住以下几点：
不要忘记明确区分安装前和安装后配置指令（即使它们位于同一个文档中） - 您希望最大程度地减少最终用户出错的风险（无论您多么努力，其中一些人都会这样做）。
The readme should be a separate file that sits beside the MSI on the media you distribute the web app on. This is a standard practice dating from
generations agothe dark ages. If you distribute as a download from the web then have a link for the MSI, and a link for the readme.You could also include the same file into the MSI, but arguably that is the wrong place for it as the user has yet to reach the configuration stage, and unless they print it they won't be able to refer to it later in the MSI process (if you have any configuration steps in the MSI).
Having the instructions available via the web app is also arguably wrong, as the user may have to do some initial configuration in order to reach the page telling them how to configure the app....
So ship the instructions separately to the MSI, and make sure they look okay and are easily readable when printed out. Remember these pointers:
Don't forget to clearly distinguish between pre-install and post-install configuration instructions (even if they are in the same document) - you want to minimize the risk of the end user getting it wrong (which some of them will do no matter how hard you try).
将重要消息构建到您的应用程序中。像 Apache 一样，它说“这是......的新安装”，并且不要让该屏幕消失，直到他们进入并执行所有您认为重要的事情。
这不是安装程序需要解决的问题。
Build the important message into your application. Do it like Apache where it says "this is a new installation of...." and don't allow that screen to go away until they go in and do all the things that you consider important.
This isn't a problem for your installer to solve.