![]() ![]() There are basically two scenarios here - having a deployed web site (no source code) and working with the nopCommerce source code. All versions of nopCommerce prior to 2.65 reference a signed version of FluentValidation 3.2.0.0, so it is important to use the signed version of FluentValidation 3.4.6.0 as otherwise the binding redirect won't work. The signed version has a publickeytoken=a82054b837897c66, while the unsigned version has a publickeytoken=null. This way any references to the old signed FluentValidation assembly 3.2.0.0 will be redirected to the new stable signed version 3.4.6.0. ![]() The idea is to use the new signed version of the FluentValidation assembly and have a binding redirect in the Web.config file. In this blog post we will provide a step by step guide for resolving the problem, so you won't need to uprade your web sites to nopCommerce 2.65, even when your hosting provider upgrades the servers and installs. If not, then you can read the release notes of nopCommerce 2.65, which uses a newer version of FluentValidation, where the. So if you have seen this error message ": Operation could destabilize the runtime" then you are probably already aware of this issue. NET 4.5 and throws exceptions at runtime. ![]() This happens because all the previous versions of nopCommerce use a version of the FluentValidation library that is not compatible with. NET 4.5 installed it is impossible to run any nopCommerce version prior to nopCommerce 2.65. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |