我认为这并不是一个答案。

• The registry at the time of creating it looked like a good idea to store all settings for all programs in one place as oppose to the .ini files generally used before. At the time this increased performance as small .ini file reads from slow hard drives were costly, a single registry file somewhat increased performance. This is now different as hard drives are far faster and more and more settings have been dumped in the registry making it a burden on the system. You will see this if you install and uninstall lots of programs in windows it begins to slow down and eventually you probably end up reformatting.
• An incorrect write to the registry even in the current user settings can ruin your system.
• The registry doesn t help xcopy deployment of programs without specific code to handle lack of registry keys... This includes removing programs by simply deleting the folder in many cases
• Greater permissions can be needed to install an application if it needs access to the registry
• A .config file easily allows default application and user setting which can be modified on first run of the program by the end user
• Allows .NET to potentially run on other systems without OS specific code. This can somewhat be seen with Silverlight and isolated storage.
• Greater security through the use of Isolated Storage for the application and users
• Gives Microsoft the possibility way in the future to have a managed code only OS without many old dependencies. Think of the framework as a layer between any OS and the managed code.

另一个原因是,为了伪造登记处,必须获得更多的许可。 如果你只是编辑一个书状,那么你只需要拥有该书的权利。

• The registry is huge so it can be cumbersome to locate the relevant information (even with searching).
• It is possible to affect other applications by accident when modifying the registry.
• If the registry is corrupted all applications may be affected (including the OS).
• You need special purpose tools to search, modify and even copy the registry.

我倾向于混淆档案。

这是因为登记处是使用的一种ug梦,人们也这样做。 该公司还提供了支持微米部署。 在使用Xml文档进行配置后,如果不需要安装装置,你可以将一台机器转换成机器。 这在90年代是重写法典的最大投诉之一。

在登记册上,当你在很多组织禁止申请时,你必须准许修改。 为了修改申请的顺序,你还必须知道,在许多情况下,登记处很难找到哪儿。 它拥有与大多数其他材料分离的权利。 通常,你们所需要的一切环境都是容易地看待和修改的。

立即(但重要的)优势:

用户可以通过<密码>查询<>代码>配置文件,在重新安装/从备份中恢复功能的情况下,能够方便地恢复环境。 很难从登记价值中做到这一点。

转而将档案整理到登记处的一个重大优势是允许在旁边安装同一方案。 随着登记处的登记,这些重复安装的中央配置信息将重叠,但使用集束文档,信息将保存到每个具体安装。 用户组合倒置可能重叠(因为这些组合重新储存在用户数据夹中,并非具体放在安装线上),而是设想一种不同用户使用不同装置的情况,在这种情况下,这一潜在问题变得无关紧要。

我认为,造成这种情况的主要原因之一是更新申请。 当你安装更新设备(即使用ClickOnce)时,新环境实际上会进入一个新的轨道。 当你停下来时,新翻了一番,旧的环境仍然周围。 如果登记处被改用,则无法做到这一点。

其他原因包括:

• Permissions (app settings always go into AppData/LocalAppData which requires no privileges)
• Ease of maintenance/backups
• Portability (it s rather difficult to deal with the registry using the .NET Compact Framework, and god help you if you re trying to support Mono).

在我看来,登记册是“当时看起来好想法”的一件事,因为其他登记者已经列举的许多原因。 根本不正确的做法是认识到,某些东西根本不是如此伟大的思想,而是使用一种更简单、更方便的替代方法,即使这似乎在某些方面是一种倒退。

我听到了相当实质性的传说,共享点和团队基础服务器使用的数据储存格式,由SQ支持,最初旨在取代窗口档案系统。 7. 如果是计划,那么窗口本来会获得/(有时会获得)交易数据储存。 这种数据储存方法可能以各种方式优先于登记处。

鉴于这一点,它很难把登记册的使用降至最低限度,因为它们正在推进因特网框架。