XAF 与 CIIP：网站:http://www.uims.top， XAF技术博客:http://www.cnblogs.com/foreachlife/
tylike 升级到 DevExpress XAF 16.1.5，实际是：16.1.5与16.1.4的混合。
visual studio 2015 + devexpress application framework (XAF)16.1.4 + SqlServer2014
============
将 DevExpress XAF 全部升级： 16.1.6 ， 有一个错误：解决方案下\CIIP.WEB\web.config 文件升级有点问题，提示：non ASCII character found(line 76,char 5), and encoding is not specified, 需要查看官方的知识库，kb=k18172。 （！ 是一个汉字的备注的影响。）
--------------------------
升级后：1）取消： 启动项目 win 的项目属性 “签名”下的 “为Clickonce签名清单”的选择框；
2）取消：安全性下 “启动Clickonce安全设置” 的选择项。
运行项目时，出现 “程序集清单定义与程序集引用不匹配”的错误，原来引用16.1.5 不存在，修改 app.config,增加 bindingRedirect。
反正启动时，提示的引用的版本不正确的，都增加重定位到新版本。
<dependentAssembly>
<assemblyIdentity name="DevExpress.ExpressApp.v16.1" publicKeyToken="b88d1754d700e49a" culture="neutral" />
<bindingRedirect oldVersion="16.1.5.0" newVersion="16.1.6.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DevExpress.Persistent.BaseImpl.v16.1" publicKeyToken="b88d1754d700e49a" culture="neutral" />
<bindingRedirect oldVersion="16.1.5.0" newVersion="16.1.6.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DevExpress.ExpressApp.Objects.v16.1" publicKeyToken="b88d1754d700e49a" culture="neutral" />
<bindingRedirect oldVersion="16.1.5.0" newVersion="16.1.6.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DevExpress.ExpressApp.ConditionalAppearance.v16.1" publicKeyToken="b88d1754d700e49a" culture="neutral" />
<bindingRedirect oldVersion="16.1.5.0" newVersion="16.1.6.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DevExpress.ExpressApp.Validation.v16.1" publicKeyToken="b88d1754d700e49a" culture="neutral" />
<bindingRedirect oldVersion="16.1.5.0" newVersion="16.1.6.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="DevExpress.ExpressApp.Win.v16.1" publicKeyToken="b88d1754d700e49a" culture="neutral" />
<bindingRedirect oldVersion="16.1.5.0" newVersion="16.1.6.0" />
</dependentAssembly>
至少可以启动整个项目了，其它功能就慢慢试用吧。
官方 https://www.devexpress.com/Support/Center/Question/Details/K18172
The problem appears because the problematic file contains non ASCII symbols and does not contain information about its Encoding. In this instance, we cannot convert the file, because there is no way to determine the encoding used to write certain files and, consequently, it is impossible to parse such files correctly. In this situation the conversion can lead to a corruption.
Note: you may start to receive similar warning messages when upgrading to the version 10.1 or later of our suites. In version 10, we introduced the source code conversion mechanism in our ProjectConverter tool, and all source files (*.cs, *.vb) can also be processed. So, if they contain non ASCII characters while the encoding is not specified, the mentioned warning will also be shown.
To resolve this issue, you will need to perform the following operations with problematic files:
1) Open the problematic files in the VS,
2) Select the File | Save As... menu command.
3) Click the down arrow next to the Save button in the Save File As dialog and select "Save with Encoding...".
4) Choose "Unicode (UTF-8 with signature) - Codepage 65001".
5) Process your project files with our ProjectConverter tool.
We also suggest you review the K18172 thread, where you can find an automatic conversion tool kindly provided by our client - Mr. Klayton Dias
See also:
How to: Manage Files with Encoding
=============================================================
Xafari Framework : 用于面向业务应用开发的强大平台，且它是基于最先进、灵活的的DevExpress XAF平台.