Due to the design of binding in ASP.NET, you may need to reboot your computer or stop the ASP.NET process in order to clear the cache and allow the signature to correctly resolve.
Another reason for this issue is when calling the syncfusion.shared.base/any other assembly in your asp.net webapplication which is a delaysigned assembly with strong-name but haven't contained complete signature. (In our private patch 18.104.22.168 version some of dlls has this issue)
To fix this
1. Do Inform us for providing the release version with complete signature.
2. you need to turns off verification for this assembly using the following command:sn ¨CVr Syncfusion.Shared.base.dll/any assembly. But this is only for developing, if you want to use the assembly in your production, It is essential that your dll should contain strong signature.
In addition, here is the reference in MSDN which has detailedly describethe delaysign for an assembly:
|Article ID:||Published Date:||Last Revised Date:||Platform:||Control:|
|934||04/30/2011||07/10/2014||Miscellaneous||Install and Configuration|